-Don't forget to @code{#include} the various header files. In this
-example, you would need to make sure that @samp{#include "strdup.h"}
-is evaluated when compiling all source code files, that want to make
-use of @code{strdup}.
-
-When an include file is provided by Gnulib
-you shouldn't try to include the corresponding system header files
-yourself, but let the gnulib header file do it. The ordering
-of the definition for some symbols may be significant; the Gnulib
-header files take care of that.
-
-For example, to use the @code{time_r} gnulib module you should
-use include header file provided by the gnulib, and so
-@samp{#include "time_r.h"}, but you shouldn't explicitly
-@samp{#include <time.h>} as it is already done in @file{time_r.h}
-before the redefinition of some symbols.
-
-@node Modified imports
-@section Modified imports
-
-You can at any moment decide to use Gnulib differently than the last time.
-
-If you only want to use more Gnulib modules, simply invoke
-@command{gnulib-tool --import @var{new-modules}}. @code{gnulib-tool}
-remembers which modules were used last time. The list of modules that
-you pass after @samp{--import} is @emph{added} to the previous list of
-modules.
-
-For most changes, such as added or removed modules, or even different
-choices of @samp{--lib}, @samp{--source-base} or @samp{--aux-dir}, there
-are two ways to perform the change.
-
-The standard way is to modify manually the file @file{gnulib-cache.m4}
-in the M4 macros directory, then launch @samp{gnulib-tool --import}.
-
-The other way is to call @command{gnulib-tool} again, with the changed
-command-line options. Note that this doesn't let you remove modules,
-because as you just learned, the list of modules is always cumulated.
-Also this way is often impractical, because you don't remember the way
-you invoked @code{gnulib-tool} last time.
-
-The only change for which this doesn't work is a change of the
-@samp{--m4-base} directory. Because, when you pass a different value of
-@samp{--m4-base}, @code{gnulib-tool} will not find the previous
-@file{gnulib-cache.m4} file any more... A possible solution is to manually
-copy the @file{gnulib-cache.m4} into the new M4 macro directory.
-
-In the @file{gnulib-cache.m4}, the macros have the following meaning:
-@table @code
-@item gl_MODULES
-The argument is a space separated list of the requested modules, not including
-dependencies.
-
-@item gl_AVOID
-The argument is a space separated list of modules that should not be used,
-even if they occur as dependencies. Corresponds to the @samp{--avoid}
-command line argument.
-
-@item gl_SOURCE_BASE
-The argument is the relative pathname of the directory containing the gnulib
-source files (mostly *.c and *.h files). Corresponds to the
-@samp{--source-base} command line argument.
-
-@item gl_M4_BASE
-The argument is the relative pathname of the directory containing the gnulib
-M4 macros (*.m4 files). Corresponds to the @samp{--m4-base} command line
-argument.
-
-@item gl_TESTS_BASE
-The argument is the relative pathname of the directory containing the gnulib
-unit test files. Corresponds to the @samp{--tests-base} command line argument.
-
-@item gl_LIB
-The argument is the name of the library to be created. Corresponds to the
-@samp{--lib} command line argument.
-
-@item gl_LGPL
-The presence of this macro corresponds to the @samp{--lgpl} command line
-argument. It takes no arguments.
-
-@item gl_LIBTOOL
-The presence of this macro corresponds to the @samp{--libtool} command line
-argument. It takes no arguments.
-
-@item gl_MACRO_PREFIX
-The argument is the prefix to use for macros in the @file{gnulib-comp.m4}
-file. Corresponds to the @samp{--macro-prefix} command line argument.
-@end table
-
-@node Simple update
-@section Simple update
-
-When you want to update to a more recent version of Gnulib, without
-changing the list of modules or other parameters, a simple call
-does it:
-
-@smallexample
-$ gnulib-tool --import
-@end smallexample
-
-This will create, update or remove files, as needed.
-
-@node CVS Issues
-@section CVS Issues
-
-All files created by @code{gnulib-tool}, except @file{gnulib-cache.m4},
-should be treated like generated source files, like for example a
-@file{parser.c} file is generated from @file{parser.y}.
-
-In projects which commit all source files, whether generated or not, into
-CVS, the @code{gnulib-tool} generated files should all be committed.
-
-In projects which customarily omit from the CVS all files that generated
-from other source files, all these files and directories would not be
-added into CVS. The only file that must be added to CVS is
-@file{gnulib-cache.m4} in the M4 macros directory. Also, the script for
-restoring files not in CVS, customarily called @file{autogen.sh} or
-@file{bootstrap.sh}, will typically contain the statement for restoring
-the omitted files:
-
-@smallexample
-$ gnulib-tool --update
-@end smallexample
-
-The @samp{--update} option operates much like the @samp{--import} option,
-but it does not offer the possibility to change the way Gnulib is used.
-Also it does not report in the ChangeLogs the files that it had to add
-because they were missing.