I’m not exactly sure what you meant by “GPL or equivalent license”,
but I’d like to point out that using any GPL-compatible licensed code
part of a larger base of GPL code is allowed
So basically a GPL program or library can use code from, or link to a
BSD, Apache, MIT, etc. licensed library.On Mon, Sep 22, 2008 at 14:51, Sam Lantinga wrote:
On Wed, Sep 17, 2008 at 14:56 -0500, Will Langford wrote:
Standard disclaimer about excessive static linking and licensing issues. If
one of the nested libraries is GPL, you have to be GPL.
If you have an alternate download with a dynamically linked version this
would be enough to satisfy the licence.
No, is Right. You’re thinking of the LGPL. The GNU C library has a special
exception to the GPL allowing linking with it. The standard GPL requires that
all linked code also be under the GPL or equivalent license, regardless of how
it’s linked. It’s a very restrictive license that’s really only useful for
completely open source projects that only use open source code and only allow
themselves to be used in open source code. It’s viral that way.