apparently its loosely copyleft? but I was wondering if anyone could sum up what all it requires. like.. I don't want my project to have to be open source.
views:
73answers:
1
+2
A:
I am not a lawyer, this is not legal advice, this is personal opinion, and feel free to insert your own additional disclaimer(s) or jokes about said disclaimer(s) here.
To sum it up briefly: LGPL requires that for such a use case
- the library itself remain copyleft
- that you ship at least the corresponding source code for the version of the library used in your project
- that the end-user have a way to use their own modified version of the library with your project.
- and that your project's license does not prohibit reverse-engineering of your project for at least the limited purpose of debugging/troubleshooting modifications to the LGPL library.
This is normally dealt with by building the LGPL library as a shared or dynamic library (.dll or .so), although you can also ship the object files for your code so the end-user can build a new statically linked binary.
Jeffrey Hantin
2010-10-04 21:26:21
Actually the library remains copyright to the original author - copyleft is just a joke about copyright and politics.
Martin Beckett
2010-10-04 21:37:29
@Martin: I'm using the word here in the jargon sense of a copyright licensed under terms requiring reciprocal source release. See http://catb.org/jargon/html/C/copyleft.html
Jeffrey Hantin
2010-10-04 21:43:05
Yes - it was more a clarification to the OP.
Martin Beckett
2010-10-04 23:00:02