Warren Young schrieb:
> Axel Howind wrote:
>> Warren Young schrieb:
>>> Jeff Huston wrote:
>>>> What happened to libmysqlpp.a ?
>>> Since the move to the new build system, we only generate shared
>>> libraries. Due to the licensing of MySQL++, this is almost always
>>> the only one you're legally allowed to use anyway, so we don't have
>>> much incentive to provide a static library.
>> Sorry, but could you please explain this in more detail? The website
>> states MySQL++ is LGPL licensed, and whether I link my program
>> statically or dynamic, it is a derived work according to the LGPL.
> No, that's the GPL you're thinking of. (The MySQL C API library is
> GPL'd, but that's a separate matter I won't cover here.)
Now I get it. I was a little confused because prior to posting I
searched the lgpl text for "static" and the only quote I found (in v 2.1
of the license) says "When a program is linked with a library, whether
statically or using a shared library, the combination of the two is
legally speaking a combined work, a derivative of the original library."
But of course you are right, static linking requires your program to
have a lgpl or compatible license. Just that the word "static" doesn't
appear in that paragraph of the lgpl. ;-)