1 --- automake-1.8.orig/automake.1
2 +++ automake-1.8/automake.1
4 +.\" Copyright (C) 1992, 1993, 1994, 1995, 1996 Free Software Foundation, Inc.
5 +.\" Copyright (C) 1998 Ben Pfaff.
7 +.\" Permission is granted to make and distribute verbatim copies of
8 +.\" this manual provided the copyright notice and this permission notice
9 +.\" are preserved on all copies.
11 +.\" Permission is granted to copy and distribute modified versions of this
12 +.\" manual under the conditions for verbatim copying, provided that the entire
13 +.\" resulting derived work is distributed under the terms of a permission
14 +.\" notice identical to this one.
16 +.\" Permission is granted to copy and distribute translations of this manual
17 +.\" into another language, under the above conditions for modified versions,
18 +.\" except that this permission notice may be stated in a translation approved
19 +.\" by the Foundation.
21 +.TH AUTOMAKE 1 "28 Jan 2002"
23 +automake - automatically create Makefile.in's from Makefile.am's
64 +.BR --output-dir= DIR
66 +.BR --srcdir-name= DIR
82 +for a package, run the
84 +program in the top level directory, with no arguments.
86 +will automatically find each appropriate
90 +and generate the corresponding
94 +has a rather simplistic view of what constitutes a package; it assumes
95 +that a package has only one
98 +top. If your package has multiple
102 +in each directory holding a
105 +You can optionally give
109 +is appended to the argument and the result is used as the name of the
110 +input file. This feature is generally only used to automatically
111 +rebuild an out-of-date
115 +must always be run from the topmost directory of a project, even if
116 +being used to regenerate the
118 +in some subdirectory. This is necessary
125 +uses the knowledge that a
127 +is in a subdirectory to change its behavior in some cases.
130 +accepts the following options:
135 +Automake requires certain common files to exist in certain
136 +situations; for instance
141 +.BR AC_CANONICAL_HOST .
142 +Automake is distributed with several of these files; this option will
143 +cause the missing ones to be automatically added to the package,
144 +whenever possible. In general if Automake tells you a file is
145 +missing, try using this option. By default Automake tries to make a
146 +symbolic link pointing to its own copy of the missing file; this can
147 +be changed with \fB--copy\fP.
150 +Look for Automake data files in directory DIR instead of in the
151 +installation directory. This is typically used for debugging.
156 +When used with \fB--add-missing\fP, causes installed files to be copied.
157 +The default is to make a symbolic link.
160 +Causes the generated
162 +to follow Cygnus rules, instead of GNU or Gnits rules.
167 +When used with \fB--add-missing\fP, causes standard files to be rebuilt
168 +even if they already exist in the source tree.
169 +This involves removing the file from the source tree before creating the
170 +new symlink (or, with \fB--copy\fP, copying the new file).
173 +Set the global strictness to
177 +Set the global strictness to
181 +Set the global strictness to
183 +This is the default strictness.
186 +Print a summary of the command line options and exit.
191 +This disables the dependency tracking feature.
194 +This enables the dependency tracking feature. This feature is
195 +enabled by default. This option is provided for historical
196 +reasons only and probably should not be used.
205 +This option causes it to only update those
207 +which are out of date with respect to one of their dependents.
211 +.BI --output-dir=\fRDIR
214 +in the directory DIR. Ordinarily
217 +is created in the directory of the
220 +This option is used when making
226 +Cause Automake to print information about which files are being read
230 +Print the version number of Automake and exit.
236 +will cause all warnings issued by
238 +to become errors. Errors affect the exit status of
239 +\fIautomake\fP, while warnings do not.
240 +\fB--Wno-error\fP, the default, causes warning to be treated as warnings only.
244 +and the Texinfo documentation for automake
246 +Automake was written primarily by David Mackenzie and Tom Tromey.
247 +This manpage written by Ben Pfaff <pfaffben@pilot.msu.edu> for the
252 --- automake-1.8.orig/aclocal.1
253 +++ automake-1.8/aclocal.1
255 +.\" Copyright (C) 1992, 1993, 1994, 1995, 1996 Free Software Foundation, Inc.
256 +.\" Copyright (C) 1998 Ben Pfaff.
258 +.\" Permission is granted to make and distribute verbatim copies of
259 +.\" this manual provided the copyright notice and this permission notice
260 +.\" are preserved on all copies.
262 +.\" Permission is granted to copy and distribute modified versions of this
263 +.\" manual under the conditions for verbatim copying, provided that the entire
264 +.\" resulting derived work is distributed under the terms of a permission
265 +.\" notice identical to this one.
267 +.\" Permission is granted to copy and distribute translations of this manual
268 +.\" into another language, under the above conditions for modified versions,
269 +.\" except that this permission notice may be stated in a translation approved
270 +.\" by the Foundation.
272 +.TH ACLOCAL 1 "Automake"
274 +aclocal - automatically generate aclocal.m4 from configure.in
292 +Automake includes a number of Autoconf macros which can be used in
293 +your package; some of them are actually required by Automake in certain
294 +situations. These macros must be defined in your
296 +otherwise they will not be seen by
301 +program will automatically generate
303 +files based on the contents of
305 +This provides a convenient way to get Automake-provided macros,
306 +without having to search around. Also, the
308 +mechanism is extensible for use by other packages.
314 +files it can find, looking for macro definitions. Then it scans
316 +Any mention of one of the macros found in the first step causes that
317 +macro, and any macros it in turn requires, to be put into
322 +if it exists, are also automatically included in
324 +This is useful for incorporating local macros into
328 +accepts the following options:
331 +Look for the macro files in DIR instead of the installation
332 +directory. This is typically used for debugging.
335 +Print a summary of the command line options and exit.
338 +Add the directory DIR to the list of directories searched for
342 +.BI --output=\fRFILE
343 +Cause the output to be put into FILE instead of
347 +Print the names of the files it examines.
350 +Print the version number of Automake and exit.
354 +and the Texinfo documentation for automake
356 +Automake was written primarily by David Mackenzie and Tom Tromey.
357 +This manpage written by Ben Pfaff <pfaffben@pilot.msu.edu> for the