On Wed, Jun 11, 2008 at 05:16:13PM -0700, Michael O'Keefe wrote:
Their runtime is GPL with exception so people can make proprietary
applications. They've removed the GPL exception from the publically
available runtime, but people the old versions still work. You can also
use the newest version if a GPL runtime works for you.
So if you use the GPL'd toolchain to _compile_ your application, you
have to GPL your application, unless you pay them money?
That's the sort of behavior that really pissed me off when proprietary
companies did such things.
Aren't .so's supposed to get around that ?
That's how our lawyers approach it. We can't use any .a libraries
But if they don't release any .so's, whachagonnado !?
.so's do _not_ get around the GPL. The whole point of the LGPL is that you
can link a proprietary program against a LGPL .so. Releasing a proprietary
binary against a GPL .so is a violation of the GPL.
David
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
