From: Kinsella, Ray <ray.kinsella@intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] autotools, pkg_config and mysql_config
Date: Thu, 24 Mar 2016 20:25:02 +0000 [thread overview]
Message-ID: <1458851101.3496.13.camel@intel.com> (raw)
Hi folks,
So I have a library (radlib) which can link against a couple of database libraries; sqlite, mysql and postgresql. I have been sorting out it's autotools implementation.
SQLite - worked like a dream, with two lines in my configure.ac
PKG_CHECK_MODULES([SQLITE3], [sqlite3], [have_libsqlite3=yes], [have_libsqlite3=no])$
AM_CONDITIONAL([LIB_SQLITE3], [test "$have_libsqlite3" = "yes"])$
However mysql, in an effort to be slightly different - doesn't use pkg_config, so you therefore can't use PKG_CHECK_MODULES. Instead it ships its own tool mysql_config.
So I wrote some autoconf, to handle that ...
AX_WITH_PROG([MYSQL_CONFIG], [mysql_config], [AC_MSG_ERROR(mysql_config is required to build)])$
if test "x$MYSQL_CONFIG" != "x";then$
AC_CHECK_HEADERS([mysql.h mysql/mysql.h])$
if test "x$ac_cv_header_mysql_h" != "xno" -o "x$ac_cv_header_mysql_mysql_h" != "xno" ; then$
MYSQL_CFLAGS=`$MYSQL_CONFIG --cflags`$
MYSQL_LIBS=`$MYSQL_CONFIG --libs`$
AC_SUBST([MYSQL_CFLAGS])$
AC_SUBST([MYSQL_LIBS])$
fi$
fi$
AM_CONDITIONAL([LIB_MYSQL], [test "x$mysql_config" != "x"])
My problem is that, it is continually picking myconfig from my host system. So end up with $MYSQL_CONFIG=/usr/bin/mysql_config instead of target/usr/bin/mysql_config. MYSQL_CFLAGS and MYSQL_LIBS therefore also end up pointing at the host.
pkg_config works fine it gets set to target/usr/bin/pkg_config.
Have tried the other similar autotools macros (https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Generic-Programs.html) - problem remains the same. Any clues for me?
Ray K
next reply other threads:[~2016-03-24 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 20:25 Kinsella, Ray [this message]
2016-03-25 15:38 ` [Buildroot] autotools, pkg_config and mysql_config Thomas Petazzoni
2016-03-25 15:50 ` Kinsella, Ray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1458851101.3496.13.camel@intel.com \
--to=ray.kinsella@intel.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox