关于MySQL ++，GPL和LGPL [英] About MySQL++, GPL and LGPL

问题描述

MySQL ++是通过LGPL许可的，这意味着我可以发布与它动态链接的可执行文件，而不必担心源代码不是GPL. 但是，MySQL ++确实链接到libmysqlclient {_r}.{a，so}( http://tangentsoft.net/mysql ++/#linkerrors )进行了GPL处理.
如图所示，从技术上讲，MySQL ++只是对GPLed libmysqlclient {_r}的包装器"(很好地实现了包装，不要误解我).{a，so}，如果我针对MySQL ++进行链接就像对libmysqlclient {_r}.{a，so}?

MySQL++ is licensed though LGPL, that means that I could release an executable dynamically linked against it without worrying about the source code not being GPL. But, MySQL++ DOES link against libmysqlclient{_r}.{a,so} ( http://tangentsoft.net/mysql++/#linkerrors ) which is GPLed.
As seen as then MySQL++ is technically just a 'wrapper' (btw a very well implemented wrapper, don't get me wrong) towards the GPLed libmysqlclient{_r}.{a,so}, if I link against MySQL++ is like linking against libmysqlclient{_r}.{a,so}?

如果是这种情况，那么MySQLLG被LGPL的目的就毫无意义，因为任何动态链接到该可执行文件的可执行文件都必须链接到libmysqlclient {_r}.{a，so}.我哪里错了?

If this is the case, then the purpose of MySQL++ being LGPLed is pointless as seen as then any executable dynamically linking against it MUST be then linked against libmysqlclient{_r}.{a,so} as well. Where am I wrong?

推荐答案

如果您的程序是根据MySQL发行版EXCEPTIONS-CLIENT文件中列出的许可证之一获得许可的，则您的程序不必是GPL-兼容使用MySQL客户端库.

If your program is licensed under one of the licences listed in the EXCEPTIONS-CLIENT file in the MySQL distribution, then your program doesn't have to be GPL-compatible to use the MySQL client library.

但是总的来说，是的，如果您要链接到GPL库，则您的程序必须与GPL兼容.

But in general, yes, if you want to link to a GPL library then your program has to be GPL-compatible.

这篇关于关于MySQL ++，GPL和LGPL的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！