* doc/libtool.texi (Invoking libtoolize): Improve documentation

for use of ACLOCAL_AMFLAGS and AC_CONFIG_MACRO_DIR.

diff --git a/ChangeLog b/ChangeLog
index 8bbf334cbbabcc6c3fdb2e8128ac36fee60941c2..297c3b67367ff21b3791f42a3672e2df0764c1d2 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2004-11-22  Gary V. Vaughan  <gary@gnu.org>
+
+       * doc/libtool.texi (Invoking libtoolize): Improve documentation
+       for use of ACLOCAL_AMFLAGS and AC_CONFIG_MACRO_DIR.
+
 2004-11-22  Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
 
        * m4/libtool.m4 (_LT_TAG_COMPILER): Document that with_gcc is

diff --git a/doc/libtool.texi b/doc/libtool.texi
index 5db2acddf2350c30c8fcaa007db3b0c96e4b059c..3be2601f2733f2746c09357a475b22809cf45a16 100644 (file)
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -2222,6 +2222,28 @@ If @command{libtoolize} detects an explicit call to
 autoconf, The Autoconf Manual}) in your @file{configure.ac}, it will
 put the Libtool macros in the specified directory.
 
+In the future other Autotools will automatically check the contents of
+@code{AC_CONFIG_MACRO_DIR}, but at the moment it is more portable to
+add the macro directory to @code{ACLOCAL_AMFLAGS} in
+@file{Makefile.am}, which is where the tools currently look.  If
+@command{libtoolize} doesn't see @code{AC_CONFIG_MACRO_DIR}, it too
+will honour the first @samp{-I} argument in @code{ACLOCAL_AMFLAGS}
+when choosing a directory to store libtool configuration macros in.
+It is perfectly sensible to use both @code{AC_CONFIG_MACRO_DIR} and
+@code{ACLOCAL_AMFLAGS}, as long as they are kept in synchronisation.
+
+@example
+ACLOCAL_AMFLAGS = -I m4
+@endif
+
+When you bootstrap your project with @command{aclocal}, then you will
+need to explicitly pass the same macro directory with
+@command{aclocal}'s @samp{-I} flag:
+
+@example
+trick$ @kbd{aclocal -I m4}
+@end example
+
 @findex AC_CONFIG_AUX_DIR
 If @command{libtoolize} detects an explicit call to
 @code{AC_CONFIG_AUX_DIR} (@pxref{Input, , The Autoconf Manual,