54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
-
+
|
## <a name="mysqlclientgpl"></a>Doesn’t the MySQL C API library’s GPL license override MySQL++’s LGPL license?
The MySQL C API library is available under *two* different licenses, not one.
The default license for MySQL (including its C API library) is GPL with the FOSS license exception. This is what you get if you got MySQL for free, such as by downloading it from `mysql.com` or as part of your Linux distro. The less liberal distribution terms of the C API library’s GPL do override the less restrictive ones of MySQL++’s LGPL license. This matters if you want to distribute your program as a binary only, keeping the source to yourself.
If you need to be able to distribute closed-source programs, Oracle. will happily sell you a [commercial distribution
If you need to be able to distribute closed-source programs, Oracle will happily sell you a [commercial distribution
license](http://www.mysql.com/about/legal/licensing/oem/) for their C API library.
This issue really has nothing to do with MySQL++. The same restriction applies if you write your program directly against the C API library. The only reason I even put this here is because people keep asking the question. Please work out the licensing with Oracle. Having settled that, the previous FAQ item applies.
## <a name="conncpp"></a>How does MySQL++ compare to MySQL’s Connector/C++?
|