Author: wyoung
Date: Thu Dec 16 15:58:43 2010
New Revision: 2681
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2681&view=rev
Log:
Added static library build instructions
Modified:
trunk/README-Unix.txt
Modified: trunk/README-Unix.txt
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/README-Unix.txt?rev=2681&r1=2680&r2=2681&view=diff
==============================================================================
--- trunk/README-Unix.txt (original)
+++ trunk/README-Unix.txt Thu Dec 16 15:58:43 2010
@@ -85,3 +85,34 @@
See the chapter on threading in the user manual for more
details and advice on creating thread-safe programs with
MySQL++.
+
+
+Building a Static Library
+~~~~~~~~~~~~~~~~~~~~~~~~~
+ As shipped, MySQL++ only builds a shared library. It's possible
+ to change things so you get a static library instead, but we don't
+ ship it like that because of MySQL++'s LGPL license. The LGPL
+ requires that if you distribute a program in binary form, its
+ recipients have the freedom to replace the LGPL parts themselves.
+ There are a couple of ways to do that, but the easiest is to
+ dynamically link to the LGPL parts.
+
+ This means that if you build MySQL++ as a static library, you
+ can't legally distribute binaries linked against it. Unlike with
+ the MySQL Connector/C and Connector/C++ libraries, there is no
+ commercial exception available for MySQL++ because there is not
+ a single copyright holder on MySQL++. So, this option is suited
+ only for those building programs that won't be distributed, such
+ as one building internal programs for a corporation, which are
+ not distributed outside the corporation.
+
+ The necessary changes are all in mysql++.bkl:
+
+ - Change the <dll> tag to <lib>. (Remember the closing tag!)
+
+ - Remove the <dllname> tag
+
+ - Remove the <so_version> tag
+
+ Then, re-bootstrap the library. See HACKERS.txt if you've never
+ done that before.
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits