Linked by Thom Holwerda on Fri 13th Mar 2009 08:28 UTC
Permalink for comment 353070
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
More News »
Sponsored Links



Member since:
2005-11-06
As far as I know, you *can't* statically link an LGPL library without releasing your own software under the same license, you can only do that if you link dynamically. OTOH, in the case of a GPL library, as opposed to LGPL, you can't link at all unless your software is released as GPL too.
I think the static vs. dynamic is an artificial distinction and that no library should actually be released as LGPL: either select GPL, that forces everyone to adopt your license or release it under a BSD/MIT license that gives developers the freedom to link however they prefer and later release using their favorite license.