Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3BA91AB1.70607@ece.gatech.edu>
Date: Wed, 19 Sep 2001 18:22:41 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: [ANN] dllhelpers-0.2.8 available
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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/