On Wed, 15 Oct 2008 08:57:01 -0700 Barry Leslie <Barry.Leslie@xxxxxxxxxxxxx> wrote: >Hi, > >I work on plug-ins for MySQL and building a plug-in out side of the MySQL >tree requires that you configure your build with the same compiler settings >as the MySQL build that you are targeting. > >To do this I have created a macro that uses a --with-mysql configuration >option to give it the location the local MySQL build. This macro then reads >the config.status file from the MySQL build to get the build flags of >interest. > >The problem of course is that the format of config.status is not constant >and every time some one finds a format I haven't come across yet I need to >update the macro to handle it. Yet I've never built MySQL by myself, but I think recent popular solution (around freedesktop related field) would be pkgconfig. When building a library A, configure in the source package of A generates A.pc and the installer copies A.pc to /usr/share/pkgconfgi or /usr/lib/pkgconfig. Afterwards, a builder of application B can retrieve the appropriate CFLAGS/LDFLAGS to link library A by the commands like "pkg-config A --cflags". So I think making MySQL provides pkgconfig file would be generic solution for developers. If we can modify configure.ac of MySQL and update configure, it won't be too hard to add mysql.pc, but I guess the update of configure script may make many building-only people troubled. Your target developers are sufficiently familiar with the process of modify-and-update autoconf stuffs? Regards, mpsuzuki _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
