[opensource-dev] LGPL violation
Carlo Wood
carlo at alinoe.com
Thu Oct 28 04:29:11 PDT 2010
On Wed, Oct 27, 2010 at 10:17:01AM -0400, Oz Linden (Scott Lawrence) wrote:
> On 2010-10-23 7:27, Carlo Wood wrote:
> > I am not a lawyer :p, but I think that it is allowed to link an LGPL-ed
> > library statically against a proprietary executable provided you
> > provide the object code or source code of the work that uses the library.
>
> Not correct. LGPL code may be linked to other source without having the
> viral effect of requiring that other source also be published as open
> source. LGPL _does_ require that if any changes are made to the source
> under that license, then those changes (and the original sources) must
> be open and available either as LGPL or as GPL.
You state pretty firmly, while I believe you are in error.
You are NOT allowed to link statically with an LGPL-ed library unless you
provide the means for the user to relink the library, for example by
providing the .o (object) files that it is linked with.
More information about the opensource-dev
mailing list