Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <3FF7F6D5.30409@keypro.fi>
Date: Sun, 04 Jan 2004 13:19:49 +0200
From: Jani Tiainen <jani.tiainen@keypro.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
MIME-Version: 1.0
To: Karl Robillard <krobillard@cox.net>
CC: cygwin@cygwin.com
Subject: Re: DLL vs. shared object linking behavior
References: <200401031753.32396.krobillard@cox.net>
In-Reply-To: <200401031753.32396.krobillard@cox.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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/