List:MySQL++« Previous MessageNext Message »
From:Axel Howind Date:August 4 2007 9:26am
Subject:MySQL++ licensing (was: 2.1.1 -> 2.3.2 ... libmysqlpp.a no longer
exists)
View as plain text  
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
Thread
2.1.1 -> 2.3.2 ... libmysqlpp.a no longer existsJeff Huston31 Jul
  • RE: 2.1.1 -> 2.3.2 ... libmysqlpp.a no longer existsJeff Huston1 Aug
  • failing row[] assignmentJeff Huston1 Aug
    • Re: failing row[] assignmentDrew M.1 Aug
      • Re: failing row[] assignmentJeff Huston2 Aug
        • Re: failing row[] assignmentWarren Young2 Aug
          • Re: failing row[] assignmentJeff Huston3 Aug
            • Re: failing row[] assignmentWarren Young3 Aug
              • Re: failing row[] assignmentJeff Huston3 Aug
  • Re: 2.1.1 -> 2.3.2 ... libmysqlpp.a no longer existsWarren Young2 Aug
    • MySQL++ licensing (was: 2.1.1 -> 2.3.2 ... libmysqlpp.a no longerexists)Axel Howind4 Aug
      • Re: MySQL++ licensingWarren Young6 Aug
        • Re: MySQL++ licensingAxel Howind6 Aug