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


On Tue, Nov 19, 2013 at 05:46:37PM +0100, Alex Thurgood wrote:

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

and GNU/Linux, and probably also MacOS X.

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

I have tried using :

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

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

Something like:

export CFLAGS='-I/path/to/mysql_cppconn/includes'
export LDFLAGS='-L/path/to/mysql_cppconn/libs'
./autogen.sh --enable-ext-mariadb-connector --with-system-mysql-cppconn

OR

export MARIADBCONFIG=/path/to/mariadb_config_or_mysql_config
./autogen.sh --enable-ext-mariadb-connector --without-system-mysql-cppconn --with-system-mariadb

you can add --enable-bundle-mariadb if the libmysql/libmariadb is not
in the default search path (else, you need to set rpath manually or
run LibreOffice under
 export LD_LIBRARY_PATH=/path/to/libmysqlclient.so.15
or something like that).


BUT, I have some good news. The (LGPL) MariaDB native client developer
fixed the crash, so we if we update to bzr revision 107 (or later), we
can switch back to mariadb native client... Except it does not quite
inspire confidence, I'm not sure...

-- 
Lionel

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.