Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Sun, 27 Jun 1999 23:10:51 -0400
To:	DJ Delorie <dj AT delorie DOT com>
Cc:	khan AT xraylith DOT wisc DOT EDU, cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Re: running two independent Cygwin DLLs?
Message-ID:	<19990627231051.B8904@cygnus.com>
References:	<199906280258 DOT VAA23658 AT mercury DOT xraylith DOT wisc DOT edu> <199906280305 DOT XAA00938 AT envy DOT delorie DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.3i
In-Reply-To:	<199906280305.XAA00938@envy.delorie.com>; from DJ Delorie on Sun, Jun 27, 1999 at 11:05:57PM -0400

On Sun, Jun 27, 1999 at 11:05:57PM -0400, DJ Delorie wrote:
>
>>     * have a different name, say cygwin1-test.dll, and regenerate the
>>       import library accordingly, so that the newly linked apps will 
>>       refer to this instead.
>
>Hmmm... Makefile and cygwin.din should do it.  Also change
>cygwin.din's BASE to avoid relocation overhead.

This shouldn't be an issue should it?  There's only going to be one DLL linked
into the process address space at any time.

>>     * change the shared address and name so that the new DLL won't
>>       see the values for the stock one.
>
>You'll also need to change some of the version parameters in
>winsup/include/cygwin/version.h to use a different shared memory
>region and/or other shared resources.  Note that this means that a
>parent using one dll will treat a child using the other dll as a
>non-cygwin program, and visa versa.

Actually, all you have to do is "configure --enable-debugging".  That
will cause the shared memory regions to be named based on the date/time.

cgf

- Raw text -