Per> .java files, and thus be able to generate a list of
Per> .class files from a list of .java source files.
-From Jason Molenda:
-* allow a way to use "gzip --best"
- [ Try GZIP=--best make dist ]
-* don't assume GNU tar is "tar" (eg in distcheck)
-
!! Must fix require_file stuff. It is really gross, and I don't
understand it any more.
what goes in AC_CONFIG_AUX_DIR
-TEXINFO_TEX
-
multi-":" mode in AC_OUTPUT -- automake only looks at the first file
also a note on how a .am file is found in this case
Automake probably can't do all of this on its own. A new tool might
be a better idea
+I have some notes from a Debian developer on how the integration
+should work
+
================================================================
A tool to guess what the local Makefile.am should look like:
@ifinfo
This file documents GNU automake @value{VERSION}
-Copyright (C) 1995, 96 Free Software Foundation, Inc.
+Copyright (C) 1995, 96, 97 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
the same directory as the Texinfo source. However, if you used
@code{AC_CONFIG_AUX_DIR} in @file{configure.in}, then @file{texinfo.tex}
is looked for there. Automake supplies @file{texinfo.tex} if
-@samp{--add-missing} is given. The option @samp{no-texinfo.tex} can be
-used to eliminate the requirement for @file{texinfo.tex}; this is useful
-if manuals appear in many directories.
+@samp{--add-missing} is given.
+
+If your package has Texinfo files in many directories, you can use the
+variable @code{TEXINFO_TEX} to tell automake where to find the canonical
+@file{texinfo.tex} for your package. The value of this variable should
+be the relative path from the current @file{Makefile.am} to
+@file{texinfo.tex}:
+
+@example
+TEXINFO_TEX = ../doc/texinfo.tex
+@end example
+
+The option @samp{no-texinfo.tex} can be used to eliminate the
+requirement for @file{texinfo.tex}. Use of the variable
+@code{TEXINFO_TEX} is preferable, however, because that allows the
+@code{dvi} target to still work.
Automake generates an @code{install-info} target; some people apparently
use this. By default, info pages are installed by @samp{make install}.