Bundling with a Non GPL compiler
BlitzCoder last edited by BlitzCoder
I’m planning to bundle Notepad++ editor in a package, instead of having to download it separately with a Non GPL compiler tool and other stuff.
Will there be any licensing issues?
I’m not sure I fully understand the question, but you should know the GPL is a source code license. It has nothing to do with compiled executable programs, or the tools used to compile them.
The GPL does not even prohibit charging a fee to download or use compiled versions of GPL-covered software (*); proprietary Linux operating systems like RHEL are just one example. As long as the source code is freely available, you can do anything you want with the finished product.
[ . . . ]
Each contributor grants you a non-exclusive, worldwide, royalty-free patent
license under the contributor’s essential patent claims, to make, use, sell,
offer for sale, import and otherwise run, modify and propagate the contents
of its contributor version.
https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3)#fulltext (emphasis added)
dail last edited by
@rdipardo said in Bundling with a Non GPL compiler:
It has nothing to do with compiled executable programs
There are still terms that apply to the compiled executable programs. Section 6 (and 4 and 5) of the GPLv3 actually covers the required terms to distribute the ‘object form’ of GPL licensed software.
Section 6 (and 4 and 5) of the GPLv3 actually covers the required terms to distribute the ‘object form’ of GPL licensed software.
All true. However those sections were drafted in the days of CD-ROMs and 3.5" diskettes. Nowadays, you “convey” the source by hosting it on GitHub.
Granted, Linux package maintainers do bundle the source files and make scripts; but only because their package policies are as old as the GPL itself.