running two independent Cygwin DLLs?

[Chris Faylor]

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