* Java:: Java bytecode compilation (deprecated)
* Python:: Python
+Python
+
+* Supported Python versions::
+
Building documentation
* Texinfo:: Texinfo
* Checking the Distribution:: @samp{make distcheck} explained
* The Types of Distributions:: A variety of formats and compression methods
+Checking the Distribution
+
+* DISTCHECK_CONFIGURE_FLAGS:: Overriding configure flags in distcheck.
+* distcheck-hook:: Running commands after distcheck.
+* dvi and distcheck:: Overriding the distcheck doc target.
+* distcleancheck:: Handling files not cleaned.
+* distuninstallcheck:: Overriding the uninstall check.
+* Errors with distclean::
+
Support for test suites
* Generalities about Testing:: Concepts and terminology about testing
* Make verbosity:: Make is verbose by default
* Tricks For Silencing Make:: Standard and generic ways to silence make
* Automake Silent Rules:: How Automake can help in silencing make
+* Unsilencing Automake:: Showing commands.
When Automake Isn't Enough
* maintainer-mode:: missing and AM_MAINTAINER_MODE
* Wildcards:: Why doesn't Automake support wildcards?
* Limitations on File Names:: Limitations on source and installed file names
-* Errors with distclean:: Files left in build directory after distclean
* Flag Variables Ordering:: CFLAGS vs.@: AM_CFLAGS vs.@: mumble_CFLAGS
* Renamed Objects:: Why are object files sometimes renamed?
* Per-Object Flags:: How to simulate per-object flags?
@end enumerate
@noindent
-If needed, Gettext-related tools (@pxref{,,,gettext, GNU gettext
-utilities}) may be invoked at different points. Thus, all in all,
-using @command{autoreconf} is quite a bit more convenient.
+If needed, tools related to Gettext (@pxref{,,,gettext, GNU gettext
+utilities}) and Libtool (@pxref{,,,libtool, GNU libtool}) are also
+invoked at different points. Thus, as you can see, using
+@command{autoreconf} is quite a bit more convenient.
Nevertheless, because Autoconf and Automake have separate manuals, an
essential idea to understand is that Autoconf is in charge of creating
@cindex Including @file{Makefile} fragment
@cindex @file{Makefile} fragment, including
-Automake supports an @code{include} directive that can be used to
+Automake supports an @code{include} directive that can be used to
include other @file{Makefile} fragments when @command{automake} is run.
Note that these fragments are read and interpreted by @command{automake},
not by @command{make}. As with conditionals, @command{make} has no idea that
* maintainer-mode:: missing and AM_MAINTAINER_MODE
* Wildcards:: Why doesn't Automake support wildcards?
* Limitations on File Names:: Limitations on source and installed file names
-* Errors with distclean:: Files left in build directory after distclean
* Flag Variables Ordering:: CFLAGS vs.@: AM_CFLAGS vs.@: mumble_CFLAGS
* Renamed Objects:: Why are object files sometimes renamed?
* Per-Object Flags:: How to simulate per-object flags?