Mercurial > hg > octave-nkf > gnulib-hg
changeset 11444:9d49a57f4a8c
Document how gnulib-tool can be put into PATH.
author | Bruno Haible <bruno@clisp.org> |
---|---|
date | Thu, 02 Apr 2009 02:20:00 +0200 |
parents | 1319abc494f3 |
children | 66a365760f8b |
files | ChangeLog doc/gnulib-tool.texi |
diffstat | 2 files changed, 18 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2009-04-01 Bruno Haible <bruno@clisp.org> + + * doc/gnulib-tool.texi (Invoking gnulib-tool): Document how gnulib-tool + can be put into PATH. + Reported by Reuben Thomas <rrt@sc3d.org>. Suggested by Karl Berry. + 2009-04-01 Bruno Haible <bruno@clisp.org> * doc/lib-symbol-visibility.texi: Follow texinfo style conventions.
--- a/doc/gnulib-tool.texi +++ b/doc/gnulib-tool.texi @@ -1,7 +1,7 @@ @node Invoking gnulib-tool @chapter Invoking gnulib-tool -@c Copyright (C) 2005-2008 Free Software Foundation, Inc. +@c Copyright (C) 2005-2009 Free Software Foundation, Inc. @c Permission is granted to copy, distribute and/or modify this document @c under the terms of the GNU Free Documentation License, Version 1.3 or @@ -21,6 +21,17 @@ simplifies the management of source files, @file{Makefile.am}s and @file{configure.ac} in packages incorporating Gnulib modules. +@file{gnulib-tool} is not installed in a standard directory that is +contained in the @code{PATH} variable. It needs to be run directly in +the directory that contains the Gnulib source code. You can do this +either by specifying the absolute filename of @file{gnulib-tool}, or +you can also use a symbolic link from a place inside your @code{PATH} +to the @file{gnulib-tool} file of your preferred and most up-to-date +Gnulib checkout, like this: +@smallexample +$ ln -s $HOME/gnu/src/gnulib.git/gnulib-tool $HOME/bin/gnulib-tool +@end smallexample + Run @samp{gnulib-tool --help} for information. To get familiar with @command{gnulib-tool} without affecting your sources, you can also try some commands with the option @samp{--dry-run}; then