Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi all,

I used to be able to build a functional mysql connector on MacOSX by
using the build switch :

--enable-ext-mariadb-connector

However, the inclusion of a build-time downloaded libmariadb library was
stopped after this caused crashes on Window

If you run the above switch now on OSX, you get the following message :

libmariadb is known to be broken as of 2013-10; use libmysqlclient

and configure stops without completing.


So the million dollar question now is : which switch is to be used now ?

On my Linux systems, I don't seem to have any problem building the
connector extension, I imagine because libmysqlclient is included on the
machines in question (because I'm running mysql client and server),
along with libmysqlcppconn.

However, on Mac OSX, these are not included by default. I have
downloaded the MySQL C connector library source, and also have a copy of
libmysqlcppconn for OSX, but how do I tell autogen.sh to use them ?

I have tried using :

--with-system-mysql-cppconn=/path/to/lib/

and removing the --enable-ext-mariadb-connector

but if I do this, the connector fails to get built. I see a mysql
connector directory in the extensions directory, but it doesn't contain
any of the libs and isn't assembled into an OXT, unlike say, NLPSolver.
I suspect this is due to the externalisation of these extensions.



Alex




Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.