Top priorities:
+* DOCUMENT
* Must rewrite am_install_var. Should break into multiple functions.
This will allow the callers to be a little smarter.
* Rewrite clean targets.
+Make HEADERS obsolete
+
+Think about ways to make automake fit better with Cygnus-style trees.
+
Handle MAINT_CHARSET. Use recode in dist target. Handle dist-zoo and
dist-zip.
configure scanning
putting .h files into blah_SOURCES is ok now
version.texi handling
+gettext support
+all options
================================================================
other than the gee-whiz factor?
Would it be useful to integrate in some way with the Debian package
-building utility? Must check.
+building utility? Must check. maybe it would be possible to deal
+with all the different package utilities somehow.
This causes @file{hello.o} to be built from @code{hello.c} at compile
time, and then linked into @file{hello}.
+If @samp{@var{prog}_SOURCES} is not specified, then it defaults to the
+single file @samp{@var{prog}.c}.
+
Multiple programs can be built in a single directory -- simply list them
all in the @samp{PROGRAMS} definition. Multiple programs can share a
single source file. The source file must be listed in each ``_SOURCES''
Sometimes, multiple programs are built in one directory but do not share
the same link-time requirements. In this case, you can use the
@samp{@var{prog}_LDADD} variable (where @var{PROG} is the name of the
-program as it appears in @samp{PROGRAMS} to override the global
+program as it appears in @samp{PROGRAMS}) to override the global
@samp{LDADD}. (If this variable exists for a given program, then that
program is not linked using @samp{LDADD}.)
@example
bin_SCRIPTS = automake
-
-automake: automake.in
- CONFIG_FILES=$@@ CONFIG_HEADERS= ./config.status
@end example
+FIXME xref to rebuilding things listed in AC_OUTPUT
+
Script objects can be installed in @samp{bindir}, @samp{sbindir}, or
@samp{libexecdir}.
@section Building Libraries
The @samp{LIBRARIES} variable holds the names of libraries to be built
-in the current directory. If the libraries to be built vary at
-configure time, you may define @samp{AM_LIBRARIES} to supply
-@code{automake} with the full static list of possible libraries.
+in the current directory.
For a given library @samp{zot}, the sources are taken to be in
@samp{zot_SOURCES}, just as for programs. Note that libraries and
@samp{--include-deps} also turns off inclusion of the dependency
generation code.
-There should probably be a way to suppress this mode.
+This mode can be suppressed by putting @samp{no-dependencies} in the
+variable @samp{AUTOMAKE_OPTIONS}.
@node Options
@item dist-shar
Generate a @samp{dist-shar} target as well as the ordinary @samp{dist}
target.
+
+@item no-dependencies
+Never include dependencies in the generated @file{Makefile.in}.
@end table
@node Extending