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 Message-ID: <3B546188.38BB1D3E@bestweb.net> Date: Tue, 17 Jul 2001 12:02:16 -0400 From: "James E. LaBarre" X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: CYGWIN1.DLL References: <20010717143212 DOT B730 AT cygbert DOT vinschen DOT de> <20010717152323 DOT F730 AT cygbert DOT vinschen DOT de> <3B544E79 DOT 50A10401 AT bestweb DOT net> <20010717111017 DOT E9167 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit OK, I meant that the difference between Mingw & regular Cygwin is that Mingw makes a simpler install for newbies, while using cygwin.dll, etc. allows you to make use of all the other functionality of cygwin (bash, command line utils, etc.). It's a tradeoff of what your intended target is. Christopher Faylor wrote: > > 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." -- 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/