Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 18 Jul 2001 01:01:52 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: CYGWIN1.DLL Message-ID: <20010718010152.A12943@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20010717153310 DOT A10822 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.19i On Wed, Jul 18, 2001 at 08:41:26AM +0400, Andrej Borsenkow wrote: >yOn Tue, 17 Jul 2001, Christopher Faylor wrote: > >> On Tue, Jul 17, 2001 at 10:09:49AM -0700, Eric M. Monsler wrote: >> >But, I did want to point out that there are good reasons for desiring a >> >statically linked executable that are not in violation of the cygwin >> >license. >> >> I don't think I've seen a good reason for this in this thread. >> >> The fact that you could have two disparate versions of the cygwin DLL >> on your system is not, in any way, an argument for a statically linked >> cygwin. Conflicts between two versions of cygwin have nothing to >> do with the DLLness of Cygwin. >> > >Actually, it is very good argument *against* static linking. In this case >nothing can help if you have two different programs linked with two >different versions. Somebody will have to rebuild every single program >with new version of Cygwin as soon it is released ... nightmare. Right! Good point. >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. cgf -- 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/