What's the difference between Windows' DLLs and Linux' "shared objects"?
 

Hi all,

Can someone tell me the difference between dll files and shared objects ???
Is the dll file also position independent like shared objects ???

Also suggest some good articles explaining difference between windows and Linux ???

Please help... Thanks in advance

Regards
_Linux_Learner

AFAIR, "native" .dlls (as opposed to .NET assemblies) don't support backreferences (linux .so does)...

I can't give you any articles, sorry. Just one IMHO interesting difference: While linux completely follows the idea of a modular, but "monolithic", kernel, windows NT kernel was created with the microkernel principles in mind (but, for performance reasons, drivers and "kernel daemons" also run in ring-0, so it's not a real microkernel architecture)

For a really basic start, press F1 for the Gnome help program and run through the desktop User Guide to see which things are different.

If you need to use OpenOffice, its help system has a page "Comparing Microsoft Office and OpenOffice.org Terms" which is useful.

This site has a wiki which includes a guide to equivalent programs in the two systems.

The major differences are a product of history and usage. Linux is an imitation of Unix, a system created for mainframes, and it runs on the majority of servers. Windows was created for the pc, and runs on the majority of desktops. That explains some built-in differences like Linux's clear distinction between root and ordinary users, and high level of security. The fact that Linux is almost all open-source explains why most programs have dependencies (support files shared with others), while Windows software comes in complete packages. That in turn explains why Linux programs don't get installed in a single folder, but spread all over the place: a binary here, a library there, a document somewhere else. And the multi-user background explains why their configuration files are in the user's folder.

I've virtually no experience of Windows, but I've lived through CPM, MSDOS, QDOS, and Linux: like the insurance adverts say, change happens, and you'll get used to it in time.

More help required on this topic... still not clear

Please help... Thanks in advance...

Regards
_Linux_Learner

Well, it is true that you did not get a direct answer to the question of dlls vs shared objects. BUT--You do not acknowledge the inputs you have already been given, and you do not state exactly what additional help you need.

1. Have you done any Google searches using "DLL" or "shared object"?

2. Have you done any searches here at LQ--or on Google--using "Windows vs. Linux"?

Please post the relevant parts of your own research, and the specific topic that you do not understand.

Hi,

You've been on the LQ forums for awhile now. You should know that we will aid you when you help yourself to a solution. Provide us with what you have attempted and then maybe someone will be able to assist.

'How to Ask Questions the Smart Way' would be one link you should look at to help us to help you in the future.

'Linux Tutorial - Static, Shared Dynamic and Loadable Linux Libraries' is the result of 'dll files and shared objects' <Linux> - Google Search from your original post.

:hattip:

*Learner;
You might also consider sticking around for a few minutes after posting a question.

http://www.linuxquestions.org/questi...thread-606415/

This thread looks like a duplicate of the one linked to.

Hi,

How?

Just a poor title by a newbie who should changed the title to suit the questions presented.
:hattip:

Depends on the code.

If it is using platform-specific calls (win32 api) -- better forget it, you would have to rewrite it. Of course it SHOULD be usable with wine, but only for windows executables running in wine, too.

If the code is only using libc and POSIX calls, it is platform-independent and you can create a .so simply by compiling and linking it with gcc on linux, but it is quite unlikely to find completely portable source for a windows dll...