This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: DLL vs. shared object linking behavior
- From: Jani Tiainen <jani dot tiainen at keypro dot fi>
- To: Karl Robillard <krobillard at cox dot net>
- Cc: cygwin at cygwin dot com
- Date: Sun, 04 Jan 2004 13:19:49 +0200
- Subject: Re: DLL vs. shared object linking behavior
- References: <200401031753.32396.krobillard@cox.net>
Karl Robillard wrote:
I have a shared library which has undefined references to functions. On Linux
I can build and use the library without problems, but when I build it as a
DLL using Cygwin the undefined references are link errors. Can the Windows
loader handle unresolved symbols in DLLs at runtime? Is there some magic
compiler option I can use to allow this?
Well I've been struggling with same things.
Problem is that windows doesn't allow direct undefined references in
DLL's. So you have to do some magic.
Look reply chain titled "DLL and external symbols", there is some
information that got me through.
Jani Tiainen
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/