delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/09/20/16:13:30

Message-Id: <200109202013.QAA22598@delorie.com>
Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: "Mark Paulus" <commpg AT yahoo DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date: Thu, 20 Sep 2001 14:13:27 -0600
Reply-To: "Mark Paulus" <commpg AT yahoo DOT com>
X-Mailer: PMMail 2000 Professional (2.20.2350) For Windows 2000 (5.0.2195;2)
In-Reply-To: <3BA91AB1.70607@ece.gatech.edu>
MIME-Version: 1.0
Subject: Re: [ANN] dllhelpers-0.2.8 available

I have a question about the examples.  In the Makefile
(for c_and_c++, and c++ at least), there is a reference in
building the objs to the variable DLL_CFLAGS.  However, 
this does not look like it ever gets set, nor does it appear to 
have a value during make execution.  

My question is, is this merely a holdover from some previous
versions that got dropped, but the comments never got
removed, or does this variable need to have a value, 
and if so, under what conditions?

Thanks.



On Wed, 19 Sep 2001 18:22:41 -0400, Charles Wilson wrote:

>I've updated the dllhelpers package at cygutils
>
>http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/dll-stuff/
>
>The new version no longer uses the '--enable-auto-image-base' function 
>of the linker; it seems to cause problems under cygwin.  Instead, 
>DLL-builders should either
>
>   a) don't specifiy any image base -- just let the linker use its 
>default of 0x10000000.  Thus, all DLLs will have the same image base, 
>and the windows runtime linker will relocate them when an application 
>loads them.  However, they won't then conflict with the cygwin1.dll 
>(which is absolutely required).  Also, runtime relocation is relatively 
>inexpensive on windows.
>
>   b) explicitly specify an image base for every DLL you build (be 
>careful!).  -Wl,--image-base=0xXXXXXXXX.
>
>this is explained in the updated documentation within the dllhelpers 
>package.
>
>Also, I've added a "c_and_c++" example, with two DLL's -- one C-based 
>and one C++based -- which are both used by a single C++ client application.
>
>--Chuck
>
>
>--
>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/




--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019