List:MySQL++« Previous MessageNext Message »
From:Chris Frey Date:December 16 2010 11:06pm
Subject:Re: static library
View as plain text  
On Thu, Dec 16, 2010 at 03:46:06PM -0700, Warren Young wrote:
> On Dec 16, 2010, at 3:11 PM, Chris Frey wrote:
> 
> > Is this because the mysql C library is GPL
> 
> The recent patch only talks about the MySQL++ license, which is LGPL.  The C API
> license issues are covered in the FAQ:
> 
> 	http://tangentsoft.net/mysql++/#mysqlclientgpl

If we're just talking about the LGPL, then this part would be false, no?

+    This means that if you build MySQL++ as a static library, you
+    can't legally distribute binaries linked against it.  Unlike with

Because if you distribute the object files of the application and related
closed dependencies, then mysql++ can be modified from source, and the
application can be re-linked.

The only way I can see that mysql++ users can't get the full benefits of
the LGPL is if some other library, that mysql++ relies on, prevents it.
And this would either be the C mysql library under GPL, or the commercial
C mysql library, under some commercial license.

What am I missing? :-)

- Chris

Thread
static libraryKemin Zhou14 Dec
  • Re: static libraryWarren Young14 Dec
    • Re: static libraryKemin Zhou14 Dec
      • Re: static libraryDino Korah14 Dec
      • Re: static libraryWarren Young15 Dec
        • Re: static librarySebastian Salazar15 Dec
          • Re: static libraryKemin Zhou16 Dec
            • Re: static libraryJonathan Wakely16 Dec
            • Re: static libraryChris Morgan16 Dec
            • Re: static libraryunrouted)16 Dec
          • Re: static libraryWarren Young16 Dec
            • Re: static libraryChris Frey16 Dec
              • Re: static libraryWarren Young16 Dec
                • Re: static libraryChris Frey17 Dec
                  • Re: static libraryWarren Young17 Dec
                    • Re: static libraryChris Frey17 Dec
Re: static libraryPeter Thorson14 Dec