Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 17 Jul 2001 11:10:17 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: CYGWIN1.DLL Message-ID: <20010717111017.E9167@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010717143212.B730@cygbert.vinschen.de> <20010717152323.F730@cygbert.vinschen.de> <3B544E79.50A10401@bestweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B544E79.50A10401@bestweb.net>; from jamesl@bestweb.net on Tue, Jul 17, 2001 at 10:40:57AM -0400 On Tue, Jul 17, 2001 at 10:40:57AM -0400, James E. LaBarre wrote: >Probably to simplify installations for end users that don't have >cygwin. That said, I'd expect the -mingw method would *be* the simplest >for end users; if they specifically need cygwin functionality, then >including more of cygwin would be the way to go (having the added >benefit of being upgradable as new cygwin builds come out). Interesting speculation, but you really can't pick and choose pieces of cygwin when linking with -mno-cygwin. It's an all or nothing thing. Either use -mno-cygwin or don't. You can't do things like "Hmm. I don't want cygwin's path code but I do like fork, so I'll just load the fork part." 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/