5 ms·
you can't copy MIT-licensed files without crediting it either. And you can statically link GPL code, assuming you release the source to all app users. You migh
by chayleaf 5y ago
you can't copy MIT-licensed files without crediting it either.
And you can statically link GPL code, assuming you release the source to all app users. You might be confusing it with LGPL, which says you can link to proprietary apps dynamically, but have to release source in all other cases.
- shoozza 5y agoYou can also link to proprietary apps statically if you provide the object files: https://softwareengineering.stackexchange.com/questions/312758/does-providing-object-files-satisfy-lgpl-relink-clause#312759 https://softwareengineering.stackexchange.com/questions/3127...
- rocqua 5y agoI thought useing GPL code without modifications was acceptable without any licensing, or is that a 'lesser GPL' license?
- orra 5y agoYou're thinking on the LGPL. The GPL is the prototypical copyleft licence, designed to encourage the liberation of software, in part via its dependencies.
- still_grokking 5y agoYou can use GPL code however you want. You have only obligations when you distribute the results. Whatever you do in your private basement is completely unaffected by that. The GPL gives you freedom to do whatever you please. That's the whole point of it! When you distribute binaries resulting form work based on GPL code than the people receiving those binaries (and only them) are eligible to get alongside the source code which allows them to rebuild the binaries you distributed to them. That makes sure that those other people also have the same freedom as you to do whatever they please with the programs and code. So the GPL preserves freedom among users of GPL code.