* Introduction:: Automake's purpose
* Details:: Creating an Automake template file
* Invoking automake:: Creating a Makefile.in
+* Distributing:: Distributing generated Makefile.ins
* Future:: Some ideas for the future.
* Some index:: Index of variables
@end menu
configure time. For instance, GNU @code{cpio} only builts @code{mt} and
@code{rmt} under special circumstances.
-In this case, you must notify Automake of all the programs that can
-possibly be built, but at the same time cause the generated
+In this case, you must notify @code{Automake} of all the programs that
+can possibly be built, but at the same time cause the generated
@file{Makefile.in} to use the programs specified by @code{configure}.
This is done trivially by making the @code{PROGRAMS} variable determined
at configure time, and letting @code{automake} look in the install
notices that a @code{Makefile.in} is out of date.
+@node Distributing
+@chapter Distributing @file{Makefile.in}s
+
+Automake places no restrictions on the distribution of the resulting
+@file{Makefile.in}s. We still encourage software authors to distribute
+their work under terms like those of the GPL, but doing so is not
+required to use Automake.
+
+Some of the files that can be automatically installed via the
+@samp{--install-missing} switch do fall under the GPL; examine each file
+to see.
+
+
@node Future
@chapter Some ideas for the future