1 --- automake-1.12/doc/automake.texi.orig 2012-04-21 16:38:05.000000000 +0200
2 +++ automake-1.12/doc/automake.texi 2012-05-09 15:48:51.421519783 +0200
7 -@dircategory Software development
8 +@dircategory Programming tools:
10 -* Automake: (automake). Making GNU standards-compliant Makefiles.
13 -@dircategory Individual utilities
15 -* aclocal-invocation: (automake)aclocal Invocation. Generating aclocal.m4.
16 -* automake-invocation: (automake)automake Invocation. Generating Makefile.in.
17 +* Automake: (automake). Making GNU standards-compliant Makefiles
18 +* aclocal-invocation: (automake)aclocal. Generating aclocal.m4
19 +* automake-invocation: (automake)automake. Generating Makefile.in
24 * Autotools Introduction:: An Introduction to the Autotools
25 * Generalities:: General ideas
26 * Examples:: Some example packages
27 -* automake Invocation:: Creating a Makefile.in
28 +* automake:: Creating a Makefile.in
29 * configure:: Scanning configure.ac, using aclocal
30 * Directories:: Declaring subdirectories
31 * Programs:: Building programs and libraries
34 * Requirements:: Configuration requirements
35 * Optional:: Other things Automake recognizes
36 -* aclocal Invocation:: Auto-generating aclocal.m4
37 +* aclocal:: Auto-generating aclocal.m4
38 * Macros:: Autoconf macros supplied with Automake
40 Auto-generating aclocal.m4
42 When starting a new project, we suggest you start with such a simple
43 @file{configure.ac}, and gradually add the other tests it requires.
44 The command @command{autoscan} can also suggest a few of the tests
45 -your package may need (@pxref{autoscan Invocation, , Using
46 +your package may need (@pxref{autoscan, , Using
47 @command{autoscan} to Create @file{configure.ac}, autoconf, The
51 would be chosen by automake; they would be @file{false-true.o} and
52 @file{true-true.o}. (The name of the object files rarely matters.)
54 -@node automake Invocation
56 @chapter Creating a @file{Makefile.in}
57 @c This node used to be named "Invoking automake". This @anchor
58 @c allows old links to still work.
61 * Requirements:: Configuration requirements
62 * Optional:: Other things Automake recognizes
63 -* aclocal Invocation:: Auto-generating aclocal.m4
64 +* aclocal:: Auto-generating aclocal.m4
65 * Macros:: Autoconf macros supplied with Automake
68 @@ -3136,11 +3132,11 @@
69 @code{m4_include} is seldom used by @file{configure.ac} authors, but
70 can appear in @file{aclocal.m4} when @command{aclocal} detects that
71 some required macros come from files local to your package (as opposed to
72 -macros installed in a system-wide directory, @pxref{aclocal Invocation}).
73 +macros installed in a system-wide directory, @pxref{aclocal}).
77 -@node aclocal Invocation
79 @section Auto-generating aclocal.m4
80 @c This node used to be named "Invoking automake". This @anchor
81 @c allows old links to still work.
85 The environment variable @env{WARNINGS} is honored in the same
86 -way as it is for @command{automake} (@pxref{automake Invocation}).
87 +way as it is for @command{automake} (@pxref{automake}).
91 @@ -3633,12 +3629,12 @@
93 @code{ACLOCAL_AMFLAGS} contains options to pass to @command{aclocal}
94 when @file{aclocal.m4} is to be rebuilt by @command{make}. This line is
95 -also used by @command{autoreconf} (@pxref{autoreconf Invocation, ,
96 +also used by @command{autoreconf} (@pxref{autoreconf, ,
97 Using @command{autoreconf} to Update @file{configure} Scripts,
98 autoconf, The Autoconf Manual}) to run @command{aclocal} with suitable
99 -options, or by @command{autopoint} (@pxref{autopoint Invocation, ,
100 +options, or by @command{autopoint} (@pxref{autopoint, ,
101 Invoking the @command{autopoint} Program, gettext, GNU gettext tools})
102 -and @command{gettextize} (@pxref{gettextize Invocation, , Invoking the
103 +and @command{gettextize} (@pxref{gettextize, , Invoking the
104 @command{gettextize} Program, gettext, GNU gettext tools}) to locate
105 the place where Gettext's macros should be installed. So even if you
106 do not really care about the rebuild rules, you should define
107 @@ -4081,8 +4077,8 @@
108 releases, you should not use any of them in new code. @emph{All
109 these macros will be removed in the next major Automake version};
110 if you are still using them, running @command{autoupdate} should
111 -adjust your @file{configure.ac} automatically (@pxref{autoupdate
112 -Invocation, , Using @command{autoupdate} to Modernize
113 +adjust your @file{configure.ac} automatically (@pxref{autoupdate,
114 +, Using @command{autoupdate} to Modernize
115 @file{configure.ac}, autoconf, The Autoconf Manual}).
118 @@ -5462,7 +5458,7 @@
119 passed to the tool invoked by @command{libtool} (hence the use of
120 @samp{@var{library}_LDFLAGS} for libtool linking flags). Generic
121 options include @option{--tag=@var{tag}} and @option{--silent}
122 -(@pxref{Invoking libtool, , Invoking @command{libtool}, libtool, The
123 +(@pxref{libtool, , Invoking @command{libtool}, libtool, The
124 Libtool Manual} for more options) should appear before the mode
125 selection on the command line; in @file{Makefile.am}s they should
126 be listed in the @samp{@var{library}_LIBTOOLFLAGS} variable.
127 @@ -5536,7 +5532,7 @@
128 Since Automake 1.6, it has been decided that running
129 @command{libtoolize} was none of Automake's business. Instead, that
130 functionality has been moved into the @command{autoreconf} command
131 -(@pxref{autoreconf Invocation, , Using @command{autoreconf}, autoconf,
132 +(@pxref{autoreconf, , Using @command{autoreconf}, autoconf,
133 The Autoconf Manual}). If you do not want to remember what to run and
134 when, just learn the @command{autoreconf} command. Hopefully,
135 replacing existing @file{bootstrap.sh} or @file{autogen.sh} scripts by
136 @@ -10296,7 +10292,7 @@
137 @cindex Option, @option{-W@var{category}}
138 @cindex Option, @option{--warnings=@var{category}}
139 These options behave exactly like their command-line counterpart
140 -(@pxref{automake Invocation}). This allows you to enable or disable some
141 +(@pxref{automake}). This allows you to enable or disable some
142 warning categories on a per-file basis. You can also setup some warnings
143 for your entire project; for instance, try @samp{AM_INIT_AUTOMAKE([-Wall])}
144 in your @file{configure.ac}.
145 @@ -10906,7 +10902,7 @@
146 that is not required by POSIX 2008 but is widely supported in
147 practice. The @option{silent-rules} option thus turns off warnings
148 about recursive variable expansion, which are in turn enabled by
149 -@option{-Wportability} (@pxref{automake Invocation}). On the rare
150 +@option{-Wportability} (@pxref{automake}). On the rare
151 @command{make} implementations that do not support nested variable
152 expansion, whether rules are silent is always determined at configure
153 time, and cannot be overridden at make time. Future versions of POSIX
154 @@ -11133,7 +11129,7 @@
155 settings of Automake, or replace some of its rules. Overriding
156 Automake rules is often inadvisable, particularly in the topmost
157 directory of a package with subdirectories. The @option{-Woverride}
158 -option (@pxref{automake Invocation}) comes in handy to catch overridden
159 +option (@pxref{automake}) comes in handy to catch overridden
162 Note that Automake does not make any distinction between rules with
163 @@ -11581,7 +11577,7 @@
166 The use of @option{--force-missing} ensures that auxiliary tools will be
167 -overridden by new versions (@pxref{automake Invocation}).
168 +overridden by new versions (@pxref{automake}).
170 It is important to regenerate all these files each time Automake is
171 upgraded, even between bug fixes releases. For instance, it is not