Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin 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>
Subject: Re: Importing symbols from .exe's
References: <Pine DOT GSO DOT 4 DOT 33 DOT 0211121644370 DOT 5111-100000 AT magic DOT shiman DOT com>
	<013401c28a98$a2fc48e0$78d96f83 AT pomello>
From: Jesper Eskilson <jojo AT virtutech DOT com>
Date: 13 Nov 2002 11:20:45 +0100
In-Reply-To: <013401c28a98$a2fc48e0$78d96f83@pomello>
Message-ID: <u67smy5zs76.fsf@sebastian.uppsala.vtech>
Lines: 17
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"Max Bowsher" <maxb AT ukf DOT 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/