MySQL++ licensing (was: 2.1.1 - > 2.3.2 ... libmysqlpp.a no longer exists) 2007-08-04 - By Axel Howind
Back
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. So
what's the (legal, not technical) difference in using the shared instead
of the dynamic library?
As to why we prefer the static lib: We have several different servers
and a mix of different applications running on these servers. Some of
the applications run for a long time without being updated, some are
updated more often. Here, it used to be more convenient to link the
MySQL++ statically, so we don't have to cope with different .so files on
our servers.
Axel
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsub=mysql@(protected)
|
|
