Doc clarification.

diff --git a/ChangeLog b/ChangeLog
index 0c9e14f8d8a55852fb3ca386da182340f8c3b854..f7c7482f373b5e2756b08aab5683c9469afa48c8 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2010-03-01  Bruno Haible  <bruno@clisp.org>
+
+       * doc/gnulib-tool.texi (Initial import): Clarify the requirements
+       regarding Automake.
+
 2010-02-25  Bruno Haible  <bruno@clisp.org>
 
        Fix breakage of gnulib-tool with ksh, introduced on 2010-02-21.

diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index 9a597e172f0774b0a886d3595736d437c535e6d4..39081801c3e8dc6e83c3eae180b0d06e595c2567 100644 (file)
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -81,8 +81,14 @@ module that contains this source file, you can use the command
 @section Initial import
 @cindex initial import
 
-Gnulib assumes your project uses Autoconf and Automake.  Invoking
-@samp{gnulib-tool --import} will copy source files, create a
+Gnulib assumes that your project uses Autoconf.  When using Gnulib, you
+will need to have Autoconf and Automake among your build tools.  Note that
+while the use of Automake in your project's top level directory is an
+easy way to fulfil the Makefile conventions of the GNU coding standards,
+Gnulib does not require it.  But when you use Gnulib, Automake will be
+used at least in a subdirectory of your project.
+
+Invoking @samp{gnulib-tool --import} will copy source files, create a
 @file{Makefile.am} to build them, generate a file @file{gnulib-comp.m4} with
 Autoconf M4 macro declarations used by @file{configure.ac}, and generate
 a file @file{gnulib-cache.m4} containing the cached specification of how