+2001-05-31 Tom Tromey <tromey@redhat.com>
+
+ * automake.texi (Top level): Removed erroneous spaces. Documented
+ MAKE and MAKEFLAGS.
+
2001-05-29 Tom Tromey <tromey@redhat.com>
* m4/init.m4 (AM_INIT_AUTOMAKE): Allow any AM_*FLAGS variable.
Then in your @file{configure.in} you can specify:
@example
-MY_SUBDIRS = "src doc lib po"
+MY_SUBDIRS="src doc lib po"
AC_SUBST(MY_SUBDIRS)
@end example
contents of this variable.
If @code{SUBDIRS} is defined, then your @file{configure.in} must include
-@code{AC_PROG_MAKE_SET}.
+@code{AC_PROG_MAKE_SET}. When Automake invokes @code{make} in a
+subdirectory, it uses the value of the @code{MAKE} variable. It passes
+the value of the variable @code{AM_MAKEFLAGS} to the @code{make}
+invocation; this can be set in @file{Makefile.am} if there are flags you
+must always pass to @code{make}.
+@vindex MAKE
+@vindex MAKEFLAGS
The use of @code{SUBDIRS} is not restricted to just the top-level
@file{Makefile.am}. Automake can be used to construct packages of
(@samp{postfix}). However, it is possible to change this ordering. You
can do this by putting @samp{.} into @code{SUBDIRS}. For instance,
putting @samp{.} first will cause a @samp{prefix} ordering of
-directories.
+directories. All @samp{clean} targets are run in reverse order of build
+targets.
Sometimes, such as when running @code{make dist}, you want all possible
subdirectories to be examined. In this case Automake will use