Hi,
Ben Walton asked:
> I'm wondering whether its feasible to use gnulib in a project that
> doesn't use autoconf/automake?
I'm adding this clarification to the documentation:
2010-03-01 Bruno Haible <br...@clisp.org>
* doc/gnulib-tool.texi (Initial import): Clarify the requirements
regarding Automake.
--- doc/gnulib-tool.texi.orig Mon Mar 1 22:08:02 2010
+++ doc/gnulib-tool.texi Mon Mar 1 22:07:01 2010
@@ -81,8 +81,14 @@
@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
