------- Comment #2 from ayers at gcc dot gnu dot org 2009-03-16 07:27 -------
So the situation seems to be:
- libobjc is a static library.
- libfoo is a dll statically linked against libobjc.
- test is program which is linked both against libfoo and libobjc.
I'm guessing here since I have no experience mingw and with linking libobjc
statically, but I could imagine that you may have two copies of libobjc in your
executable each with it's own set of runtime structures, which may cause
confusion.
Is there any reason why libobjc isn't dynamically linked if you going to use
DLL's?
Note I'll still need to build a mingw compiler and look into the auto-import
warning and I'm not sure when I'll get around to it, so I haven't assigned the
bug yet in case someone else can easily test it.
Cheers,
David
--
ayers at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ayers at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39465
