On Fri, Sep 15, 2006 at 10:54:08AM +0200, Philipp Thomas wrote: > On Fri, 15 Sep 2006 09:12:54 +0200, Robert Schiele wrote: > > >Most commercial applications use the shared library version of the glibc (and > >many other libraries) and thus don't have to ship anything. You are only > >violating the license if you don't ship the object code _and_ use static > >linking. > > Oh, have I missed something? Seems I have to reread the LGPL.
It says: [...] Also, you must do one of these things: a) Accompany the work with [...]; and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. [...] Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:[EMAIL PROTECTED] "Quidquid latine dictum sit, altum sonatur."
pgp5GWtvNFb5y.pgp
Description: PGP signature
