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: Sun, 12 Nov 2000 18:22:00 -0500 Message-Id: <200011122322.SAA15038@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj@envy.delorie.com using -f From: DJ Delorie To: cygwin@cygwin.com In-reply-to: <20001112180014.E32359@redhat.com> (message from Christopher Faylor on Sun, 12 Nov 2000 18:00:14 -0500) Subject: Re: long double support in cygwin References: <20001111232756.A26752@redhat.com> <20001112135708.A29567@redhat.com> <200011122213.RAA14479@envy.delorie.com> <20001112180014.E32359@redhat.com> > If your application uses a LGPL'ed shared library, as is the case > with glibc, you don't need to include sources. Yes if you mean "sources to your application", no if you mean "sources to the shared library". If your app uses a shared library which you do not distribute, no sources. If your app uses a shared library which you *do* distribute, you need to include sources for the shared library. If your app statically links that library, you must include sources *or* objects for your app, *and* sources for the library. > Or, at least that is my understanding of section 6b of the LGPL. If > you have linked in components of the library into your application > (i.e., cygwin) then you do. In the case of glibc, linking with it as a shared library does *not* include glibc in your program. That is not the case with cygwin, because part of cygwin *is* linked in with all programs, even though cygwin1.dll is effectively a shared library for the LGPL. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com