1 --- automake-1.10/doc/automake.texi.orig 2006-10-15 19:41:24.000000000 +0200
2 +++ automake-1.10/doc/automake.texi 2006-10-26 23:02:36.354332500 +0200
4 @c info Automake points to the Automake package's documentation
5 @c info automake points to the automake script's documentation
6 @c (Autoconf has a similar setup.)
7 -@dircategory Software development
8 +@dircategory Programming tools:
10 -* Automake: (automake). Making GNU standards-compliant Makefiles.
13 -@dircategory Individual utilities
15 -* aclocal: (automake)Invoking aclocal. Generating aclocal.m4.
16 -* automake: (automake)Invoking Automake. Generating Makefile.in.
17 +* Automake: (automake). Making GNU standards-compliant Makefiles
18 +* aclocal: (automake)aclocal. Generating aclocal.m4
19 +* automake: (automake)automake. Generating Makefile.in
24 * Autotools Introduction:: An Introduction to the Autotools
25 * Generalities:: General ideas
26 * Examples:: Some example packages
27 -* Invoking Automake:: Creating a Makefile.in
28 +* automake:: Creating a Makefile.in
29 * configure:: Scanning configure.ac or configure.in
30 * Directories:: Declaring subdirectories
31 * Programs:: Building programs and libraries
34 * Requirements:: Configuration requirements
35 * Optional:: Other things Automake recognizes
36 -* Invoking aclocal:: Auto-generating aclocal.m4
37 +* aclocal:: Auto-generating aclocal.m4
38 * Macros:: Autoconf macros supplied with Automake
40 Auto-generating aclocal.m4
42 (The name of the object files rarely matters.)
45 -@node Invoking Automake
47 @chapter Creating a @file{Makefile.in}
49 @cindex Multiple @file{configure.ac} files
52 * Requirements:: Configuration requirements
53 * Optional:: Other things Automake recognizes
54 -* Invoking aclocal:: Auto-generating aclocal.m4
55 +* aclocal:: Auto-generating aclocal.m4
56 * Macros:: Autoconf macros supplied with Automake
59 @@ -3020,13 +3016,12 @@
60 @code{m4_include} is seldom used by @file{configure.ac} authors, but
61 can appear in @file{aclocal.m4} when @command{aclocal} detects that
62 some required macros come from files local to your package (as opposed
63 -to macros installed in a system-wide directory, @pxref{Invoking
65 +to macros installed in a system-wide directory, @pxref{aclocal}).
70 -@node Invoking aclocal
72 @section Auto-generating aclocal.m4
74 @cindex Invoking @command{aclocal}
78 The environment variable @env{WARNINGS} is honored in the same
79 -way as it is for @command{automake} (@pxref{Invoking Automake}).
80 +way as it is for @command{automake} (@pxref{automake}).
84 @@ -3468,12 +3463,12 @@
86 @code{ACLOCAL_AMFLAGS} contains options to pass to @command{aclocal}
87 when @file{aclocal.m4} is to be rebuilt by @command{make}. This line is
88 -also used by @command{autoreconf} (@pxref{autoreconf Invocation, ,
89 +also used by @command{autoreconf} (@pxref{autoreconf, ,
90 Using @command{autoreconf} to Update @file{configure} Scripts,
91 autoconf, The Autoconf Manual}) to run @command{aclocal} with suitable
92 -options, or by @command{autopoint} (@pxref{autopoint Invocation, ,
93 +options, or by @command{autopoint} (@pxref{autopoint, ,
94 Invoking the @command{autopoint} Program, gettext, GNU gettext tools})
95 -and @command{gettextize} (@pxref{gettextize Invocation, , Invoking the
96 +and @command{gettextize} (@pxref{gettextize, , Invoking the
97 @command{gettextize} Program, gettext, GNU gettext tools}) to locate
98 the place where Gettext's macros should be installed. So even if you
99 do not really care about the rebuild rules, you should define
100 @@ -5314,7 +5309,7 @@
101 passed to the tool invoked by @command{libtool} (hence the use of
102 @samp{@var{library}_LDFLAGS} for libtool linking flags). Generic
103 options include @option{--tag=@var{TAG}} and @option{--silent}
104 -(@pxref{Invoking libtool, , Invoking @command{libtool}, libtool, The
105 +(@pxref{libtool, , Invoking @command{libtool}, libtool, The
106 Libtool Manual} for more options) should appear before the mode
107 selection on the command line; in @file{Makefile.am}s they should
108 be listed in the @samp{@var{library}_LIBTOOLFLAGS} variable.
109 @@ -9151,7 +9146,7 @@
110 @command{make} implementations that do not support it. The
111 @option{silent-rules} option turns off warnings about recursive variable
112 expansion, which are in turn enabled by @option{-Wportability}
113 -(@pxref{Invoking Automake}).
116 @vindex @code{AM_V_GEN}
117 @vindex @code{AM_V_at}
118 @@ -9292,7 +9287,7 @@
119 @cindex Option, @option{-W@var{category}}
120 @cindex Option, @option{--warnings=@var{category}}
121 These options behave exactly like their command-line counterpart
122 -(@pxref{Invoking Automake}). This allows you to enable or disable some
123 +(@pxref{automake}). This allows you to enable or disable some
124 warning categories on a per-file basis. You can also setup some warnings
125 for your entire project; for instance, try @samp{AM_INIT_AUTOMAKE([-Wall])}
126 in your @file{configure.ac}.
127 @@ -9840,7 +9835,7 @@
128 settings of Automake, or replace some of its rules. Overriding
129 Automake rules is often inadvisable, particularly in the topmost
130 directory of a package with subdirectories. The @option{-Woverride}
131 -option (@pxref{Invoking Automake}) comes in handy to catch overridden
132 +option (@pxref{automake}) comes in handy to catch overridden
135 Note that Automake does not make any distinction between rules with
136 @@ -10283,7 +10278,7 @@
139 The use of @option{--force-missing} ensures that auxiliary tools will be
140 -overridden by new versions (@pxref{Invoking Automake}).
141 +overridden by new versions (@pxref{automake}).
143 It is important to regenerate all these files each time Automake is
144 upgraded, even between bug fixes releases. For instance, it is not