Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Two instances of same cygwin1.dll
MIME-Version:	1.0
From:	jurgen DOT defurne AT philips DOT com
Message-ID:	<OFDB646145.3D3C0647-ONC1256F97.00298942-C1256F97.002A425B@philips.com>
Date:	Fri, 28 Jan 2005 08:40:48 +0100
X-IsSubscribed:	yes

Hello,

What I have here is not a problem, but maybe an optimalisation
for us.

We are running the WindRiver Tornado compiler, and found out
that replacing their delivered cygwin DLL with the 1.5.11 DLL
reduces/eliminates compiler crashes and gives us double the
performance.

However, when I look with the system information tool under
loaded modules, we have the same DLL twice loaded into
memory from different paths.

Can this give us other potential problems ?

I am thinking of renaming the cygwin1.dll under the Tornado
directory, so that it cannot be found there anymore, to make
the compiler use exclusively the cygwin DLL in our standard
cygwin path.

Does the Win32 API search for DLL's in the normal PATH
variable or are there other environment variables which
influence this ?

Regards,

Jurgen Defurne

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -