This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: objc: Windows DLL's won't allow unresolved symbols
- To: <gcc at gcc dot gnu dot org>, <discuss-gnustep at gnu dot org>, <mingw-users at lists dot sourceforge dot net>, <cygwin at cygwin dot com>
- Subject: Re: objc: Windows DLL's won't allow unresolved symbols
- From: "Michael Scheibler" <michael dot scheibler at onevision dot de>
- Date: Fri, 15 Jun 2001 12:55:09 +0200
- Organization: OneVision Software AG
- References: <02dd01c0f262$803ea5c0$6d07a8c0@miro> <20010611210438.A18152@piglet.bettises.com> <013301c0f31b$dede21a0$6d07a8c0@miro> <20010612061318.A2091@piglet.bettises.com>
I found no way of having ld link an Objective-C executable with undefined
references to objc class symbols on Win32 (mingw, and I think cygwin, too).
For Objective-C it's absolutely necessary, because of the late binding
capabilities of this programming language. It's not possible to use
GNUstep's bundle architecture because you have to link statically, at least
with an import library which connects to the proper DLL.
ld needs an option to just warn the user if an undefined reference to an
ObjectiveC class symbol is found.
Michael