4 ms·
To be clear, the GPL does not say anything in particular about "linking;" that's a common interpretation of what it means to be a derivative work. Wikipedia ha
by loeg 4y ago
To be clear, the GPL does not say anything in particular about "linking;" that's a common interpretation of what it means to be a derivative work. Wikipedia has a blurb on this:
> This key dispute is whether non-GPL software can legally statically link or dynamically link to GPL libraries. Different opinions exist on this issue. The GPL is clear in requiring that all derivative works of code under the GPL must themselves be under the GPL. Ambiguity arises with regards to using GPL libraries, and bundling GPL software into a larger package (perhaps mixed into a binary via static linking). This is ultimately a question not of the GPL per se, but of how copyright law defines derivative works.
https://en.wikipedia.org/wiki/GNU_General_Public_License#Linking_and_derived_works https://en.wikipedia.org/wiki/GNU_General_Public_License#Lin...
- hnfong 4y agoFew people mention it, but whether (dynamically) "linking" to a library makes it a derivative work is closely related to the GOOGLE v. ORACLE case. The issue with dynamic linking is basically "copying the API (and ABI)". Unfortunately the USSC didn't really give a clear ruling on this one.
- necovek 4y agoA more obvious case is the one of Linux (GPLv2 licensed) closed source binary modules: Linus has specifically said that he is not opposed to such usage, so it's never been tested in court either.