public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bernard Dautrevaux <Dautrevaux@microprocess.com>
To: "'Larry Hall (RFK Partners, Inc)'" <lhall@rfk.com>,
	Bernard Dautrevaux <Dautrevaux@microprocess.com>,
	"'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: CYGWIN1.DLL
Date: Wed, 18 Jul 2001 09:02:00 -0000	[thread overview]
Message-ID: <17B78BDF120BD411B70100500422FC6309E2E4@IIS000> (raw)

> -----Original Message-----
> From: Larry Hall (RFK Partners, Inc) [ mailto:lhall@rfk.com ]
> Sent: Wednesday, July 18, 2001 4:54 PM
> To: Bernard Dautrevaux; 'cygwin@cygwin.com'
> Subject: RE: CYGWIN1.DLL
> 
> 
> At 10:10 AM 7/18/2001, Bernard Dautrevaux wrote:
> > > -----Original Message-----
> > > From: Christopher Faylor [ mailto:cgf@redhat.com ]
> > > Sent: Wednesday, July 18, 2001 7:02 AM
> > > To: cygwin@cygwin.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,

Sure, but

> although that doesn't solve the potential duplication problem.

not only it doesn't solve it but worsened it if I install several programs
in several places :-)

> 
> 
> >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 problem is that cygwin can be installed *anywhere* on the system, even
on T:\quite\obscure\place :-), so finding it is not simple, then arranging
for the program to find it will require careful analysis of where
cygwin1.dll is (and which one to use if I finally find two) and where does
the PATH points then automatically modify the PATH... not so simple to say
anyone not doing this is seriously "flawed" :-)

> The latter case is still a potential issue.

Sure, and probably an important one... I don't like so much the situation
where installing a package just broke another one in some obscure way by
deleting one of its files ;-|

> 
> 
> >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 problem is that is not done by setup (for obvious reasons!) so the user
has to do it manually if needed while we would all like a solution that
avoid any manual tinkering of the user 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.

Note that distributing cygwin also requires either to setup the PATH
correctly or install your programs either with setup (the cleaner way) or at
least in th esame place as cygwin binaries (which your program is anyway),
but this is I think the only real option to obtain some automatic/universal
way to setup (no pun intended) an end-user environment.

Regards,

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

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

             reply	other threads:[~2001-07-18  9:02 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18  9:02 Bernard Dautrevaux [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-13 16:19 cygwin1.dll gothrg
2010-04-13 17:04 ` cygwin1.dll Dave Korn
2010-04-13 17:25   ` cygwin1.dll gothrog
     [not found] <4578565.268561193999540871.JavaMail.nabble@isper.nabble.com>
2007-11-02 10:50 ` Cygwin1.dll Brian Dessent
2007-11-01 23:32 Cygwin1.dll sroberts82
2007-11-01 23:46 ` Cygwin1.dll Brian Dessent
2007-11-02  0:55   ` Cygwin1.dll Charles D. Russell
2007-11-02  1:15     ` Cygwin1.dll Brian Dessent
     [not found] <434AC7D8.3050504@freemail.lt>
2005-10-10 20:05 ` cygwin1.dll Larry Hall (Cygwin)
2005-03-26 17:51 cygwin1.dll Виталий Стасюк
2005-03-26 18:32 ` cygwin1.dll Brian Dessent
     [not found] <20040710025136.A843B1BCC9@cgf.cx>
2004-07-12  0:01 ` cygwin1.dll Christopher Faylor
2004-07-10  2:52 cygwin1.dll Joshua Halls
2003-01-27 17:43 cygwin1.dll jim.a.davidson
2003-01-24 15:20 cygwin1.dll jim.a.davidson
2003-01-24 19:22 ` cygwin1.dll Igor Pechtchanski
2002-07-02  9:44 cygwin1.dll Bob Carruthers
2001-12-10  5:51 cygwin1.dll S.T. Cheok
2001-12-10  7:20 ` cygwin1.dll Collin Grady
2001-12-05  6:34 cygwin1.dll Amoediun Trepcoze
2001-12-05  7:16 ` cygwin1.dll Ronald Landheer
2001-08-28  9:25 cygwin1.dll Larry Hall (RFK Partners, Inc)
2001-08-27 17:19 cygwin1.dll Neil Lunn
2001-08-28 22:50 ` cygwin1.dll Ivan Petrovich
2001-08-29  6:06   ` cygwin1.dll Christopher Faylor
2001-08-22 20:30 cygwin1.dll Neil Lunn
2001-08-22 20:11 cygwin1.dll Jinbo Huang
2001-07-18 18:12 CYGWIN1.DLL Robert Collins
2001-07-18  9:53 CYGWIN1.DLL Mark Keil
2001-07-18  9:07 CYGWIN1.DLL Bernard Dautrevaux
2001-07-18  7:35 CYGWIN1.DLL Bernard Dautrevaux
2001-07-18  7:55 ` CYGWIN1.DLL Larry Hall (RFK Partners, Inc)
2001-07-18  8:08 ` CYGWIN1.DLL Andrej Borsenkow
2001-07-18  9:53   ` CYGWIN1.DLL Christopher Faylor
2001-07-18 18:08 ` CYGWIN1.DLL Jonadab the Unsightly One
     [not found] <995396435.30626.ezmlm@sources.redhat.com>
2001-07-17 13:12 ` CYGWIN1.DLL Joshua Franklin
2001-07-17 13:22   ` CYGWIN1.DLL Larry Hall (RFK Partners, Inc)
2001-07-17 13:24   ` CYGWIN1.DLL Christopher Faylor
2001-07-17 19:42     ` CYGWIN1.DLL Jonadab the Unsightly One
2001-07-17 20:32       ` CYGWIN1.DLL Christopher Faylor
2001-07-18  8:22         ` CYGWIN1.DLL Jonadab the Unsightly One
2001-07-17 10:45 CYGWIN1.DLL Robinow, David
2001-07-17  6:46 CYGWIN1.DLL Robinow, David
2001-07-17  8:08 ` CYGWIN1.DLL Christopher Faylor
2001-07-17  2:40 does patch.exe work different than other unx patch tools? Armin Theissen
2001-07-17  5:23 ` CYGWIN1.DLL Jnb ZI / Chris Wenk
2001-07-17  5:32   ` CYGWIN1.DLL Corinna Vinschen
2001-07-17  5:42     ` CYGWIN1.DLL Chris Wenk
2001-07-17  6:23       ` CYGWIN1.DLL Corinna Vinschen
2001-07-17  7:40         ` CYGWIN1.DLL James E. LaBarre
2001-07-17  8:07           ` CYGWIN1.DLL Corinna Vinschen
2001-07-17  8:10           ` CYGWIN1.DLL Christopher Faylor
2001-07-17  9:02             ` CYGWIN1.DLL James E. LaBarre
2001-07-17  9:09               ` CYGWIN1.DLL Christopher Faylor
2001-07-17 10:06         ` CYGWIN1.DLL Eric M. Monsler
2001-07-17 11:40           ` CYGWIN1.DLL Kurt Roeckx
2001-07-17 12:25             ` CYGWIN1.DLL Charles S. Wilson
2001-07-19  7:59               ` CYGWIN1.DLL Max Bowsher
2001-07-19 13:08                 ` CYGWIN1.DLL Michael A. Chase
2001-07-17 12:25             ` CYGWIN1.DLL Corinna Vinschen
2001-07-17 12:33           ` CYGWIN1.DLL Christopher Faylor
2001-07-17 21:41             ` CYGWIN1.DLL Andrej Borsenkow
2001-07-17 22:02               ` CYGWIN1.DLL Christopher Faylor
2001-06-17 11:33 cygwin1.dll Mark H. Siffer
2001-06-17 11:58 ` cygwin1.dll Robert Mcnulty junior
2001-06-17 14:22 ` cygwin1.dll Christopher Faylor
2001-06-08  0:33 Cygwin1.dll Thomas Weiss
2001-06-08  0:49 ` Cygwin1.dll Jean Paul Périé
2001-06-08  1:02   ` Cygwin1.dll Andrew Markebo
2001-06-08  9:13     ` Cygwin1.dll Larry Hall (RFK Partners, Inc)
2001-05-26 13:42 cygwin1.dll Cserveni Akos
2001-02-21 16:51 cygwin1.dll Kirran.Bari
2001-02-21 14:27 cygwin1.dll Kirran.Bari
2001-02-21 15:52 ` cygwin1.dll Paul Garceau
2001-02-21 15:56 ` cygwin1.dll Earnie Boyd
2001-02-21 12:27 cygwin1.dll Kirran.Bari
2001-02-21 13:52 ` cygwin1.dll Earnie Boyd
2001-02-21 15:07   ` cygwin1.dll Larry Hall (RFK Partners, Inc)
2001-02-21 15:07   ` cygwin1.dll Paul Garceau
2001-02-21 16:42     ` cygwin1.dll Earnie Boyd
2001-02-21 18:51       ` cygwin1.dll Paul Garceau
     [not found] <200102211940.OAA07959@p1fed3.frb.org>
2001-02-21 12:14 ` cygwin1.dll Earnie Boyd
2001-02-21  9:25 cygwin1.dll Kirran.Bari
2001-02-21 10:26 ` cygwin1.dll Larry Hall (RFK Partners, Inc)
2001-02-21 12:14   ` cygwin1.dll Christopher Faylor
2001-02-21 10:47 ` cygwin1.dll Earnie Boyd
2000-10-13 11:19 cygwin1.dll Earnie Boyd
2000-10-13 13:55 ` cygwin1.dll Chris Faylor
2000-10-12 10:28 cygwin1.dll Earnie Boyd
2000-10-13 10:09 ` cygwin1.dll Gerrit Haase
2000-10-13 10:19   ` cygwin1.dll DJ Delorie
2000-10-11 23:14 cygwin1.dll AGGIEMISTROT
2000-09-10  8:11 cygwin1.dll flav astraud
2000-09-10 16:18 ` cygwin1.dll MarketLogix
2000-07-12  7:05 cygwin1.dll Reynolds, John
2000-07-11 21:29 cygwin1.dll Earnie Boyd
2000-07-11 14:49 cygwin1.dll Reynolds, John
2000-07-11 18:02 ` cygwin1.dll Chris Faylor
1999-08-01 22:57 cygwin1.dll Waker
1999-08-02  1:04 ` cygwin1.dll Brendan Simon
1999-08-31 23:49   ` cygwin1.dll Brendan Simon
1999-08-31 23:49 ` cygwin1.dll Waker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17B78BDF120BD411B70100500422FC6309E2E4@IIS000 \
    --to=dautrevaux@microprocess.com \
    --cc=cygwin@cygwin.com \
    --cc=lhall@rfk.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).