Mercurial > gnulib

comparison doc/gnulib-tool.texi @ 39223:c2e83c6de345

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc: Mention another prerequisite for using Gnulib. Reported at <https://stackoverflow.com/questions/48378214/>. * doc/gnulib-tool.texi (Initial import): Mention requirement to use AC_CONFIG_HEADERS.
author Bruno Haible <bruno@clisp.org>
date Tue, 23 Jan 2018 09:13:13 +0100
parents 24e347e0e326
children 73f0573be7ff
comparison
equal deleted inserted replaced
39222:3c40257da226 39223:c2e83c6de345
84 @section Initial import 84 @section Initial import
85 @cindex initial import 85 @cindex initial import
86 86
87 Gnulib assumes that your project uses Autoconf. When using Gnulib, you 87 Gnulib assumes that your project uses Autoconf. When using Gnulib, you
88 will need to have Autoconf among your build tools. 88 will need to have Autoconf among your build tools.
89
90 Gnulib also assumes that your project's @file{configure.ac} contains the
91 line
92 @smallexample
93 AC_CONFIG_HEADERS([config.h])
94 @end smallexample
95 The @file{config.h} file gets generated with platform dependent C macro
96 definitions, and the source files include it (see @ref{Source changes}).
89 97
90 Unless you use @command{gnulib-tool}'s @option{--gnu-make} option, 98 Unless you use @command{gnulib-tool}'s @option{--gnu-make} option,
91 Gnulib also assumes that your project uses Automake at least in a 99 Gnulib also assumes that your project uses Automake at least in a
92 subdirectory of your project. While the use of Automake in your 100 subdirectory of your project. While the use of Automake in your
93 project's top level directory is an easy way to fulfil the Makefile 101 project's top level directory is an easy way to fulfil the Makefile