3 ms·
You don't have to use the GPL to link GPL code. You are just required to distribute the final binary under GPL. When you distribute the source files, individual
by zanny 10y ago
You don't have to use the GPL to link GPL code. You are just required to distribute the final binary under GPL. When you distribute the source files, individual files can be under individual licenses, they just have to all be license compatible with the final license.
IE, use GPL code, license header all your own stuff as Apache, distribute the binary as GPL, but anyone else can use your own work under Apache if they want if you are individually licensing all your own files under it, they just could not use the GPL parts without also distributing under GPL.
- eveningcoffee 10y agoDo you know a project where such licensing scheme is used as an acceptable practice? As to be honest, it looks counter productive against GPL ideas.
- halomru 10y agoIn my eyes that practise would be equivalent with dual-licensing your code under GPL and the (more liberal) license of your choice. This happens with some frequency. It's a way to honor the GPL idea for the stuff you link to without having to follow GPL ideas for your new code.
- SXX 10y agoLinux kernel is one for instance. Tons of drivers there include GPU one are permissively licensed to make it possible to reuse that code for other kernels like BSD.