Mercurial > hg > octave-nkf > gnulib-hg
changeset 13637:f4c566dd41a4
Doc update.
author | Bruno Haible <bruno@clisp.org> |
---|---|
date | Sat, 04 Sep 2010 15:28:09 +0200 |
parents | 06064a28d167 |
children | 8ae47cf4002f |
files | ChangeLog doc/gnulib-tool.texi |
diffstat | 2 files changed, 10 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2010-09-04 Bruno Haible <bruno@clisp.org> + + * doc/gnulib-tool.texi (Initial import): Update paragraph about + separate gnulib.mk. + 2010-09-04 Bruno Haible <bruno@clisp.org> gnulib-tool: Don't talk about CVS any more.
--- a/doc/gnulib-tool.texi +++ b/doc/gnulib-tool.texi @@ -145,7 +145,7 @@ By default, the source code is copied into @file{lib/} and the M4 macros in @file{m4/}. You can override these paths by using @code{--source-base=DIRECTORY} and @code{--m4-base=DIRECTORY}. Some -modules also provide other files necessary for building. These files +modules also provide other files necessary for building. These files are copied into the directory specified by @samp{AC_CONFIG_AUX_DIR} in @file{configure.ac} or by the @code{--aux-dir=DIRECTORY} option. If neither is specified, the current directory is assumed. @@ -161,11 +161,11 @@ this option is generally discouraged. @code{gnulib-tool} will overwrite any pre-existing files, in -particular @file{Makefile.am}. Unfortunately, separating the +particular @file{Makefile.am}. It is also possible to separate the generated @file{Makefile.am} content (for building the gnulib library) -into a separate file, say @file{gnulib.mk}, that could be included -by your handwritten @file{Makefile.am} is not possible, due to how -variable assignments are handled by Automake. +into a separate file, say @file{gnulib.mk}, that can be included by your +handwritten @file{Makefile.am}, but this is a more advanced use of +@code{gnulib-tool}. Consequently, it is a good idea to choose directories that are not already used by your projects, to separate gnulib imported files from