Re: [Mingw-users] Need help working around auto-import

[Carl <car...@gm...>]

On Wed, Jan 28, 2009 at 10:12 AM, Marc Vaillant <vai...@fa...> wrote:
>
>
> On Jan 27, 2009, at 10:38, Carl <car...@gm...> wrote:
>
>> Hi, I am developing a GPL program for linux which id like to port to
>> windows. The linux version has a core binary, and plugins compiled
>> into .so's which link to many of the functions within the core binary.
>> Because of the magic of ld, everything works. Under windows I had a
>> problem that I couldn't work out a way to link the .dll's to the main
>> .exe without making a serious mess.
>
> What magic are u referring to?  What's different abt windows dlls that
> did not let u do what u were doing on linux?
>
> Marc
>
A lot it seems. The most important difference is that a .dll must have
all references defined at run time, whilst a .so does not. when a .so
is loaded ld will resolve all dependencies of the .so at run time, a
.dll must know where to look for its dependencies at run time. This is
especially important when using c++, it would be an absolute pain to
export/import a class manually, with member functions and vtable etc.

Carl
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
>
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
>
> _______________________________________________
> This list observes the Etiquette found at
> http://www.mingw.org/Mailing_Lists.
> We ask that you be polite and do the same.
>
> Most annoying abuses are:
> 1) Top posting
> 2) HTML/MIME encoded mail
> 3) Improper quoting
> 4) Improper trimming
>