>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
adl> I'm installing the following patch, in an attempt to fix the
adl> rule/target usage throughout the manual.
[...]
Following a private reply from Bruno, I'm installing this.
2003-11-27 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* doc/automake.texi: More target vs. rule editing. Back out some
of the previous changes. It's OK to talk about targets as "entry
points", or as thing to build, but targets cannot be run: rules
are run.
Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.12
diff -u -r1.12 automake.texi
--- doc/automake.texi 27 Nov 2003 19:53:49 -0000 1.12
+++ doc/automake.texi 27 Nov 2003 21:42:07 -0000
@@ -4244,10 +4244,10 @@
@unnumberedsubsec Recording dependencies manually
Usually people are happy enough with @code{BUILT_SOURCES} because they
-never run rules such as @code{make foo} before @code{make all}, as in
-the previous example. However if this matters to you, you can avoid
[EMAIL PROTECTED] and record such dependencies explicitly in the
[EMAIL PROTECTED]
+never build targets such as @code{make foo} before @code{make all}, as
+in the previous example. However if this matters to you, you can
+avoid @code{BUILT_SOURCES} and record such dependencies explicitly in
+the @file{Makefile.am}.
@example
bin_PROGRAMS = foo
@@ -4711,8 +4711,8 @@
@cindex Rule, noinstall-info
@cindex Target, install-info
@cindex Target, noinstall-info
[EMAIL PROTECTED] install-info rule
[EMAIL PROTECTED] noinstall-info rule
[EMAIL PROTECTED] install-info target
[EMAIL PROTECTED] noinstall-info target
@opindex no-installinfo
@trindex install-info
@@ -4829,8 +4829,8 @@
@cindex Rule, noinstall-man
@cindex Target, install-man
@cindex Target, noinstall-man
[EMAIL PROTECTED] install-man rule
[EMAIL PROTECTED] noinstall-man rule
[EMAIL PROTECTED] install-man target
[EMAIL PROTECTED] noinstall-man target
@c Use @samp{make install} per documentation: (texi)code.
By default, man pages are installed by @samp{make install}. However,
@@ -5380,9 +5380,9 @@
@section Install Tests
-The @code{installcheck} rule is available to the user as a way to run
-any tests after the package has been installed. You can add tests to
-this by writing an @code{installcheck-local} rule.
+The @code{installcheck} target is available to the user as a way to
+run any tests after the package has been installed. You can add tests
+to this by writing an @code{installcheck-local} rule.
@node Options
@@ -5463,7 +5463,7 @@
@item @code{no-dist}
@cindex Option, no-dist
-Don't emit any code related to @code{dist} rule. This is useful
+Don't emit any code related to @code{dist} target. This is useful
when a package has its own method for making distributions.
@item @code{no-dist-gzip}
@@ -5486,7 +5486,7 @@
@cindex Option, no-installinfo
The generated @file{Makefile.in} will not cause info pages to be built
or installed by default. However, @code{info} and @code{install-info}
-rules will still be available. This option is disallowed at
+targets will still be available. This option is disallowed at
@samp{GNU} strictness and above.
@trindex info
@trindex install-info
@@ -5494,7 +5494,7 @@
@item @code{no-installman}
@cindex Option, no-installman
The generated @file{Makefile.in} will not cause man pages to be
-installed by default. However, an @code{install-man} rule will still
+installed by default. However, an @code{install-man} target will still
be available for optional installation. This option is disallowed at
@samp{GNU} strictness and above.
@trindex install-man
@@ -5600,16 +5600,15 @@
@trindex tags
At the topmost directory of a multi-directory package, a @code{tags}
-file will be generated which, when run, will generate a
[EMAIL PROTECTED] file that includes by reference all @file{TAGS} files from
-subdirectories.
+rule will be output which, when run, will generate a @file{TAGS} file
+that includes by reference all @file{TAGS} files from subdirectories.
-The @code{tags} file will also be generated if the variable
+The @code{tags} rule will also be generated if the variable
@code{ETAGS_ARGS} is defined. This variable is intended for use in
directories which contain taggable source that @code{etags} does not
understand. The user can use the @code{ETAGSFLAGS} to pass additional
-flags to @code{etags}; @code{AM_ETAGSFLAGS} is also available for use in
[EMAIL PROTECTED]
+flags to @code{etags}; @code{AM_ETAGSFLAGS} is also available for use
+in @file{Makefile.am}.
@vindex ETAGS_ARGS
@vindex ETAGSFLAGS
@vindex AM_ETAGSFLAGS
@@ -5944,7 +5943,7 @@
required.
@item
-The @code{check} rule doesn't depend on @code{all}.
+The @code{check} target doesn't depend on @code{all}.
@end itemize
GNU maintainers are advised to use @samp{gnu} strictness in preference
@@ -6168,7 +6167,7 @@
@heading What is in the API
Automake's programming interface is not easy to define. Basically it
-should include at least all @strong{documented} variables and rules
+should include at least all @strong{documented} variables and targets
that a @samp{Makefile.am} author can use, any behavior associated with
them (e.g. the places where @samp{-hook}'s are run), the command line
interface of @samp{automake} and @samp{aclocal}, @dots{}
@@ -6322,8 +6321,8 @@
@subsubheading Generated files out of CVS
One way to get CVS and @code{make} working peacefully is to never
-store generated files in CVS, i.e., do not CVS-control files which are
[EMAIL PROTECTED] rules (or @emph{derived} files in Make terminology).
+store generated files in CVS, i.e., do not CVS-controled files which
+are @code{Makefile} targets (also called @emph{derived} files).
This way developers are not annoyed by changes to generated files. It
does not matter if they all have different versions (assuming they are
--
Alexandre Duret-Lutz
