Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199904300714.CAA26077@modi.xraylith.wisc.edu>
X-Authentication-Warning: modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To: Daniel Gonzalez <dgonzalez AT datacomm DOT ch>
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Linking with several DLLs 
In-reply-to: Your message of "Fri, 30 Apr 1999 08:44:41 +0200."
             <4 DOT 2 DOT 0 DOT 32 DOT 19990430084332 DOT 00a67770 AT pop3 DOT datacomm DOT ch> 
Date: Fri, 30 Apr 1999 02:14:54 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Daniel Gonzalez <dgonzalez AT datacomm DOT ch> writes:
> Hi,
> 
> I have a program linking with several DLLs. Do I have to declare an impure 
> pointer
> in each DLL? How do I initialize it? Why is it necessary?
> 

Good news is that the impure_ptr hack hasn't been necessary since b19.1,
but you need to use the right entry point. All this is handled
transparently by dllwrap, which will eventually be obsoleted when
ld supports --shared option (thanks to DJ Delorie's ongoing work).

Please see my instructions + examples in my dllhelpers package:
  http://www.xraylith.wisc.edu/~khan/software/gnu-win32/dllhelpers.html

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com