summaryrefslogtreecommitdiff
path: root/liboil/ref/mas.c
diff options
context:
space:
mode:
authorDmitry V. Levin <ldv@altlinux.org>2010-01-04 20:54:12 +0000
committerDavid Schleef <ds@schleef.org>2010-02-04 12:20:13 -0800
commit946e7298b6db2e1821ef6a89af79c9529893fa9a (patch)
tree60296c1b0e559757b7f5b08d2409b8e244c45ac6 /liboil/ref/mas.c
parent2c13c258328321f92e7e1a40fe34506e8c855120 (diff)
downloadliboil-946e7298b6db2e1821ef6a89af79c9529893fa9a.tar.gz
Use both AC_CONFIG_MACRO_DIR and ACLOCAL_AMFLAGS
libtoolize(1) tool suggests adding AC_CONFIG_MACRO_DIR macro to configure.ac, and gtkdocize tool also uses AC_CONFIG_MACRO_DIR from configure.ac to find out where to install gtk-doc.m4 file. According to libtool documentation at http://www.gnu.org/software/libtool/manual/html_node/Invoking-libtoolize.html "If libtoolize detects an explicit call to AC_CONFIG_MACRO_DIR (see The Autoconf Manual) in your configure.ac, it will put the Libtool macros in the specified directory. In the future other Autotools will automatically check the contents of AC_CONFIG_MACRO_DIR, but at the moment it is more portable to add the macro directory to ACLOCAL_AMFLAGS in Makefile.am, which is where the tools currently look. If libtoolize doesn't see AC_CONFIG_MACRO_DIR, it too will honour the first ā€˜-Iā€™ argument in ACLOCAL_AMFLAGS when choosing a directory to store libtool configuration macros in. It is perfectly sensible to use both AC_CONFIG_MACRO_DIR and ACLOCAL_AMFLAGS, as long as they are kept in synchronisation." Fixed #25927
Diffstat (limited to 'liboil/ref/mas.c')
0 files changed, 0 insertions, 0 deletions