Inclusion of external GPL library in MIT code

I am sending software licensed under the MIT license.

In the application tree, I have a file that is part of the software. Inside this file is the exact contents of an external library licensed under the GPL. There is also another code (by me) licensed under the MIT license. The section of this file that contains the library remains intact, and the library does not change.

Can I release my software under the MIT license? Should I include a GPL license (I'm sure the answer is yes)? Should I also include README with indications such as "part of the X file is licensed under the GPL because it is an external library, the rest is MIT"?

+4
source share
2 answers

Can I release my software under the MIT license?

If you use the GPL software in your software (combine two jobs) and then distribute a new job, you must distribute it under the GPL (copyleft).

There are different options for the GPL that have different effects on the functioning of copyleft (GPL, LGPL, AGPL), so if you need more information, you need to be more specific.

Should I include a GPL license (I'm sure the answer is yes)?

Yes. Any of the GPLs requires this.

Should I also include README with indications such as "part of the X file is licensed under the GPL, as it is an external library, the rest is MIT"?

Yes, this is helpful. However, if this is really a GPL, keep in mind that next to what you write correctly, the entire package should be distributed under the GPL.

see also

+6
source

If you have a code, if you own a code property, you can change the license every time and every time you want, you can also issue the same code with more than one license.

When redistributing the code obtained from the third part released under the GPL, the only thing you need to do is to leave the license conditions unchanged, since the GPL is designed in this way. The GPL remains the GPL regardless of how many developers or entities are involved in the "distribution chain."

+1
source

All Articles