Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Wed, 24 May 2000 16:16:54 -0400
Message-Id:	<200005242016.QAA20463@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	m DOT ring AT ndh DOT net
CC:	cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to:	<rv9oiscnqopatr5af54k7mmpg6ph9v5p17@4ax.com> (message from
	Michael Ring on Wed, 24 May 2000 21:11:37 +0200)
Subject:	Re: new setup in cvs
References:	<200005241610 DOT MAA01721 AT envy DOT delorie DOT com> <rv9oiscnqopatr5af54k7mmpg6ph9v5p17 AT 4ax DOT com>

> Please keep me informed an the status of the 'new' cygwin1.dll; Igf

This isn't a new dll.  Back when I added the testsuite, I added an
option to trigger the "debug" features of the DLL via an environment
variable.  When triggered, it uses a private shared memory region
keyed off the build timestamp, so it can't interfere with other DLLs.

So all setup has to do (hopefully) is save the DLL with a unique name,
set the environment variable, and call LoadLibrary.

- Raw text -