Re:Ask HN: GPL software works but what are the cons?
by makecheck on Tuesday May 31, 2011 @01:46AM
(#2601515)
The ability to link freely isn't automatic in GPL libraries, it is something that GNU explicitly adds as an exception to the license of GCC; otherwise, GCC is pure GPL [1]. The GNU C library is a related runtime that also explicitly allows linking to proprietary software because it is under the LGPL and not the GPL [2].
What it boils down to is that GPL by itself does not allow reuse without similar disclosures of code, etc. and only a different license (like LGPL) or a documented exception to the license (like in GCC) will change that.
[1] http://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html
[2] http://www.gnu.org/s/libc/manual/html_mono/libc.html#Copying
This is a very rare situation. If you link to GPL code, then your code has to, at least, grant GPL rights to your users. However, just using GPL code to build your code is not. I use Emacs to write code that is either interpreted by Python or compiled by GCC and nothing I write needs to be licensed as GPL. A lot of OSX is compiled with GCC and many programs on the OSX install DVD are BSD licensed.
Unless you link to a GPL-only library, you are probably safe.
As for other licenses, there are licenses like BSD and Apache. You can pick code licensed under them and use it as part of proprietary code you release. OTOH, your competitor may use the BSD-ish code you release as parts of your competing product.