Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: CYGWIN1.DLL
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Thu, 19 Jul 2001 11:01:39 +1000
Message-ID: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F12B@itdomain002.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CYGWIN1.DLL
Thread-Index: AcEP7dhh1i42yOJtSTaDZXxmuaP5fgAAA9vQ
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <jonadab AT bright DOT net>, <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id VAA31291

> -----Original Message-----
> From: Jonadab the Unsightly One [mailto:jonadab AT bright DOT net]
> 
> # If I install a cygwin1.dll with my program, where should I 
> install it?
> # obviously in some directory that is in the *standard* path 
> for windows
> 
> That is not obvious.
> 
<snip>
> The problem you do NOT solve by this is that if the
> user tries to run your app and some other Cygwin app
> at the same time there can be problems in RAM, at
> runtime.  Order might matter, and other oddities.

Order won't matter. The presence of the dll in the same directory as the
program will cause it to be loaded first by windows. And the shared
memory area will most likely be different - thus causing a failure.
 
> # The only satisfying solution I've found personally is 
> # delivering a reduced (ought to be minimal but is not) 
> # cygwin install with my program (on the same CDROM).

Thats actually a good solution. Using setup.exe and only offering the
cygwin1.dll package (and sources) will mean that if the user has cygwin
already, setup won't install the old version, and if they install a
newer version of cygwin later, setup.exe will find the prior cygwin1.dll
because the mount table will be in the registry.
 
Rob

--
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/