This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Importing symbols from .exe's

From: Jesper Eskilson <jojo at virtutech dot com>
To: "Max Bowsher" <maxb at ukf dot net>
Cc: "Garrett Banuk" <mongoose at magic dot shiman dot com>, <cygwin at cygwin dot com>
Date: 13 Nov 2002 11:20:45 +0100
Subject: Re: Importing symbols from .exe's
References: <Pine.GSO.4.33.0211121644370.5111-100000@magic.shiman.com><013401c28a98$a2fc48e0$78d96f83@pomello>

"Max Bowsher" <maxb@ukf.net> writes:

> Windows' dynamic loader isn't powerful enough to do what you want. 

This is "by design", not a limitation. The idea is that DLLs should be
self-containing and not require that the loading executable/module defines
certain symbols. This is why import libraries are used; to make sure all
symbols are resolved at link-time. As a result, Windows DLLs are not
allowed to contain unresolved symbols.

A much cleaner design, IMHO.

/Jesper
-- 
Jesper Eskilson
Virtutech     
http://www.virtutech.com


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

References:
- Importing symbols from .exe's
  - From: Garrett Banuk
- Re: Importing symbols from .exe's
  - From: Max Bowsher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]