MySQLtoolazytofixtheirsharedlibrariesAPI_MySQL
来源：动视网
责编：小采
时间：2020-11-09 19:14:52
MySQLtoolazytofixtheirsharedlibrariesAPI_MySQL
MySQLtoolazytofixtheirsharedlibrariesAPI_MySQL:famzah (3425087)writesSince version 5.5 MySQL started to ship the client/server binaries statically linked against the libmysqlclient.a library. This uses more disk space and also takes away the option to fix the shared code in the libra
导读MySQLtoolazytofixtheirsharedlibrariesAPI_MySQL:famzah (3425087)writesSince version 5.5 MySQL started to ship the client/server binaries statically linked against the libmysqlclient.a library. This uses more disk space and also takes away the option to fix the shared code in the libra
famzah (3425087)writes
"Since version 5.5 MySQL started to ship the client/server binaries statically linked against the "libmysqlclient.a" library. This uses more disk space and also takes away the option to fix the shared code in the library once, rather than by recompiling every single binary which uses it.
Thesummary by Axel Schwenkefrom MariaDB is right on the target:- In the past we exported every symbol from libmysqlclient.so (this was certainly bad)
- We changed this to export only API functions (good)
- Our own (MySQL) clients use non-API functions and thus don't work with the new dynamic lib. There is a word for this: it's a bug.
- We are too lazy to fix the clients (or extend the API). So we take the short path and link the clients with the static lib. I also have a word for this: disgusting.
"
MySQLtoolazytofixtheirsharedlibrariesAPI_MySQL
MySQLtoolazytofixtheirsharedlibrariesAPI_MySQL:famzah (3425087)writesSince version 5.5 MySQL started to ship the client/server binaries statically linked against the libmysqlclient.a library. This uses more disk space and also takes away the option to fix the shared code in the libra
