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
Date: Sun, 27 Jun 1999 23:05:57 -0400
Message-Id: <199906280305.XAA00938@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: khan AT xraylith DOT wisc DOT EDU
CC: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <199906280258.VAA23658@mercury.xraylith.wisc.edu> (message from
	Mumit Khan on Sun, 27 Jun 1999 21:58:15 -0500)
Subject: Re: running two independent Cygwin DLLs?
References:  <199906280258 DOT VAA23658 AT mercury DOT xraylith DOT wisc DOT edu>


>     * 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.

>     * 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.