Software under the GPL may be run for all purposes, including commercial purposes and even as a tool for creating proprietary software, for example when using GPL-licensed compilers. Users or companies who distribute GPL-licensed works (e.g. software), may charge a fee for copies or give them free of charge.
In the GPL v2, it states "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License." If your code is completely independent of the GPL code, and is merely bundled with it, then this clause should apply.
This means you should be able to MIT if your code is using the engine but the code is independent it won't fall under the licensing
Top comments (4)
Yes indeed.
Software under the GPL may be run for all purposes, including commercial purposes and even as a tool for creating proprietary software, for example when using GPL-licensed compilers. Users or companies who distribute GPL-licensed works (e.g. software), may charge a fee for copies or give them free of charge.
Wow, thanks! I'm planning to create a software which can be used for commercial and I'll be using GPLv2 Licensed Engine available on Github.
What if all the components are GPLv2 do I need to inform the users what I use to build the software? Can I change the license for example to MIT?
In the GPL v2, it states "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License." If your code is completely independent of the GPL code, and is merely bundled with it, then this clause should apply.
This means you should be able to MIT if your code is using the engine but the code is independent it won't fall under the licensing
Alright, thanks! It helps a lot...