Prev: Can one set one's own password for root?
Next: Self Exam Engine Training - Lotus Certification | Lotus Questions and Answers
From: John Hasler on 8 Dec 2009 16:00
Lew Pitcher writes:
> If your software uses the support libraries, then you must provide the
> support libraries under the LGPL licence. This does not affect the
> licence for your software, but only the support libraries. *If* you
> make changes to the support libraries, you must release those changes
> under the LGPL.

Note, however, that the licenses for the runtime libraries include
special exceptions. An example:

The libstdc++-v3 library is licensed under the terms of the GNU
General Public License, with this special exception:

As a special exception, you may use this file as part of a free software
library without restriction. Specifically, if other files instantiate
templates or use macros or inline functions from this file, or you compile
this file and link it with other files to produce an executable, this
file does not by itself cause the resulting executable to be covered by
the GNU General Public License. This exception does not however
invalidate any other reasons why the executable file might be covered by
the GNU General Public License.


Also note that if you dynamically link to LGPL libraries (such as libc)
you needn't concern yourself about LGPL compliance as dynamic linking
inherently complies. On the other hand, if you link to GPL libraries
(such as libreadline) you may only distribute your program under the
GPL (but you have the right to not distribute it at all).
--
John Hasler
jhasler(a)newsguy.com
Dancing Horse Hill
Elmwood, WI USA
First  |  Prev  | 
Pages: 1 2
Prev: Can one set one's own password for root?
Next: Self Exam Engine Training - Lotus Certification | Lotus Questions and Answers