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
Message-Id: <4.3.1.2.20010718104537.020fe258@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 18 Jul 2001 10:54:27 -0400
To: Bernard Dautrevaux <Dautrevaux AT microprocess DOT com>,
        "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: RE: CYGWIN1.DLL
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E2E3@IIS000>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 10:10 AM 7/18/2001, Bernard Dautrevaux wrote:
> > -----Original Message-----
> > From: Christopher Faylor [mailto:cgf AT redhat DOT com]
> > Sent: Wednesday, July 18, 2001 7:02 AM
> > To: cygwin AT cygwin DOT com
> > Subject: Re: CYGWIN1.DLL
> > 
> > 
> > On Wed, Jul 18, 2001 at 08:41:26AM +0400, Andrej Borsenkow wrote:
> > >yOn Tue, 17 Jul 2001, Christopher Faylor wrote:
> > >

<snip>


> > 
> > >Probably, intelligent setup that checks for existence of cygwin dll
> > >and download/update it only if needed makes more sense.
> > 
> > Actually the current version of setup.exe has some 
> > preliminary code for
> > doing just this.
> > 
>
>The problem with relying on setup to fix that (e.g. suppressing any already
>present cygwin1.dll on the system when installing cygwin) is only part of
>the problem.
>
>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
>programs, so probably in \WINNT\system32 (as /cygwin/bin is usually NOT in
>the path for standard windows program).


No, it can go in the same directory as the program you're installing,
although that doesn't solve the potential duplication problem.


>So if I install my program AFTER cygwin, I got two cygwin1.dll and if I
>install cygwin after my program I got only one, but my program probably no
>longer run...


For the former case, this is true if the installation process for your 
program is flawed enough to ignore the existing cygwin1.dll installed by 
setup.exe.  The latter case is still a potential issue.


>I think that's part of the dreadfull DLL-HELL syndrom :-)


Yes, quite.


>Part of the problem will be avoided if setup installed cygwin1.dll in
>/WINNT/system32, but this had probably been over-discussed already :-)



Yes, it has.  Putting the Cygwin path to cygwin1.dll in the Windows path
is a better solution if you need/want to use a Cygwin program in the 
Windows environment.


>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).


This works too.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


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