Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: "Max Bowsher" Cc: "Garrett Banuk" , Subject: Re: Importing symbols from .exe's References: <013401c28a98$a2fc48e0$78d96f83@pomello> From: Jesper Eskilson Date: 13 Nov 2002 11:20:45 +0100 In-Reply-To: <013401c28a98$a2fc48e0$78d96f83@pomello> Message-ID: 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" 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/