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: Wed, 27 Dec 2000 18:59:43 -0500 Message-Id: <200012272359.SAA06445@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj@envy.delorie.com using -f From: DJ Delorie To: pgarceau@teleport.com CC: cygwin@cygwin.com In-reply-to: <3A4A0F6B.13682.39B062@localhost> (pgarceau@teleport.com) Subject: Re: Static version of Cygwin DLL? References: <3A4A0F6B.13682.39B062@localhost> > By forcing the elimination of cygwin1.dll using -mno-cygwin, > you can then do this: > > gcc -ofoo.exe foo.c -mno-cygwin -lcygwin > > The default paths already scan the usr/lib directory. It is > the usr/lib directory that has the static version of cygwin > (libcygwin.a). I'm sorry, but this is completely wrong. There is no static version of the cygwin runtime, period. The -mno-cygwin option tells gcc to cross-compile to the MSVC runtime (i.e. the result is *not* a cygwin application). What you *think* is the "static cygwin" is really just the import library for the DLL -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple