LGPL requires you to link dynamically to it, or provide full object code and linking instructions, or provide full source code and compilation instructions, for any app that links to it.

GPL requires you to GPL anything linking to it.

Cocotron ObjC runtime not thread-safe FAIL.

OneSadCookie Wrote:LGPL requires you to link dynamically to it, or provide full object code and linking instructions, or provide full source code and compilation instructions, for any app that links to it.

GPL requires you to GPL anything linking to it.

Cocotron ObjC runtime not thread-safe FAIL.

I don't use Cocotron, I just checked the gcc files it comes with because I had downloaded it previously and it was the first thing that spotlight pulled up. I'm just mentioning the license issues because Nayr got me interested in it.

As for what I was saying about the linking exception:


If I understand this correctly, and based off of what others have discussed over the issue, this exception gives you the right to link statically or dynamically with the exempt library, without holding you to any version of the GPL or its rules. It however does not exempt you if you use it for anything other than linking.

[Add] The libobjc exception is almost identical to the libstdc++ exception, that library of course is completely unrestricted in how you link to it and you are not required to do anything unless you use it in a fashion outside linking.


I hate to say it, but GPL and all its derivatives are so restrictive in their "freedom" that I've already grown to hate them. BSD-style licenses are where it's at.

Alright, an update!

I contacted the FSF (GNU organization) regarding the exception to the GPL that libobjc includes. I fortunately was right; libobjc is considered a system file so the exception allows for you to link to libobjc any way you please, statically or dynamically without having to include object files, source or anything in addition. This is all as long as you compile any program that links to it, with gcc.