From 4fc10daa05477586fea99b6b3ca02a87d1102fa1 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Mon, 1 Mar 2010 22:09:44 +0100 Subject: [PATCH] Doc clarification. --- ChangeLog | 5 +++++ doc/gnulib-tool.texi | 10 ++++++++-- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 0c9e14f8d..f7c7482f3 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2010-03-01 Bruno Haible + + * doc/gnulib-tool.texi (Initial import): Clarify the requirements + regarding Automake. + 2010-02-25 Bruno Haible 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 9a597e172..39081801c 100644 --- 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 -- 2.11.0