Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Importance:	Normal
Sensitivity:
Subject:	Re: Concurrent versions of cygwin1.dll on one system
To:	cygwin AT cygwin DOT com
Message-ID:	<OFB6CE953A.2B84CC82-ONC1256BF2.0042C72C-C1256BF2.00434917@sto.se.ibm.com>
From:	"Franz Wolfhagen" <FRANZW AT dk DOT ibm DOT com>
Date:	Wed, 10 Jul 2002 14:01:58 +0200
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g6AC29o21628

And if the commercial software does their things right that SHOULD not
cause any problems. But the real world shows differently...

But please - go ahead and place your dlls wherever you want them - just
know that nobody else than yourselfe will be able to support you.

A better idea from mt point of view is to create a specific directory for
third party tools/dlls and ensure that it os loaded in the correct sequense
(i´this means that you might have to create more than one directory for
this purpose).

BTW, one of the real good things about cygwin is that you have an
environment that is halfways isolated from your normal windows system -
this is really what gives it the big value that you do not have to worry
about dlls and other stuff as long as you stay within cygwin bash (or
whatever shell you prefer...)

Med venlig hilsen / Regards
Franz Wolfhagen


"Robert Collins" <robert DOT collins AT syncretize DOT net> on 10-07-2002 01:56:04

Please respond to "Robert Collins" <robert DOT collins AT syncretize DOT net>

To:    <cygwin AT cygwin DOT com>, Franz Wolfhagen/Denmark/IBM AT IBMDK
cc:
Subject:    Re: Concurrent versions of cygwin1.dll on one system


To get full use of cygwin1.dll I always place it's location in the system
path. Any commercial software using licenced cygwin1.dll versions may cause
trouble, but there is no excuse for folk redistributing the net release
(GPL
cywin1.dll) to conflict with the cygwin setup.exe environment.

Rob

----- Original Message -----
From: "Franz Wolfhagen" <FRANZW AT dk DOT ibm DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Tuesday, July 09, 2002 9:35 PM
Subject: Re: Concurrent versions of cygwin1.dll on one system



Be aware that there is commercial software that uses the cygwin1.dll.

One example is Tivoli Framework from IBM (which I happens to work with
proffesionally...).

To ensure that a dll is not interfering with other versions of the same dll
you must ensure that it is located in a directory that by default is NOT
included in the windows path. You should aælso familiarize yourself with
terms of dll search sequence and private dlls. This will help you
understand how to avoid conflicts of this kind.







--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -