Contents
Can a GPL program link to a proprietary library?
The case of proprietary programs linking to GPL’d libraries has been discussed thoroughly. However the inverse case – a GPL’d program is linking to a proprietary library – is rarely mentioned. Therefore my question is: Can I use a proprietary library in my own GPL’d program (which I intend to distribute) without violating the GPL?
What does a GPL linking exception do to the GPL?
A GPL linking exception modifies the GNU General Public License (GPL) in a way that enables software projects which provide library code to be ” linked to ” the programs that use them, without applying the full terms of the GPL to the using program.
Can you use GPL code without making it open source?
The answer basically says that I cannot use GPL code in any way without making my code open source. But if the previous is true then that would indicate that no person or organization could ever release any proprietary software on Linux ever.
Can a module be released under the GPL?
The GPL says that the whole combined program has to be released under the GPL. So your module has to be available for use under the GPL. But you can give additional permission for the use of your code. You can, if you wish, release your module under a license which is more lax than the GPL but compatible with the GPL.
Do you have to make GPL source available?
(b) If you do distribute YOUR APPLICATION, and you used something GPL as part of your application (even if only linking at run-time to a library) – and even if you do not charge money – and even if you do not change that GPL s/w in any way – then you MUST make the source of YOUR APPLICATION available. Making source available does not mean download.
When does your software need to be covered by the GPL?
If you release/distribute software containing GPL’d components (such as statically linked libraries), your software must be covered by the GPL. (This is the impression given for version 2; version 3 may be different.)
Can a distributed GPL program violate its own license?
Infecting means derived program violate GPL, infected means GPL program violate its own license. No problem exists when you compile a distributed GPL source as act individual (person, org, company).