+2002-06-26 Art Haas <ahaas@neosoft.com>
+
+ * automake.texi: s/.../@dots{}/.
+
2002-06-26 Alexandre Duret-Lutz <duret_g@epita.fr>
* configure.in: Check that ln works, fall back to `cp -p'.
Angus Leeming a.leeming@ic.ac.uk
Anthony Green green@cygnus.com
Arkadiusz Miskiewicz misiek@pld.ORG.PL
+Art Haas ahaas@neosoft.com
Assar Westerlund assar@sics.se
Axel Belinfante Axel.Belinfante@cs.utwente.nl
Bernard Urban Bernard.Urban@meteo.fr
@example
AC_INIT(zardoz, 1.0)
AM_INIT_AUTOMAKE
-...
+@dots{}
@end example
Since your program doesn't have any complicating factors (e.g., it
Now you must regenerate @file{configure}. But to do that, you'll need
to tell @code{autoconf} how to find the new macro you've used. The
easiest way to do this is to use the @code{aclocal} program to generate
-your @file{aclocal.m4} for you. But wait... maybe you already have an
+your @file{aclocal.m4} for you. But wait@dots{} maybe you already have an
@file{aclocal.m4}, because you had to write some hairy macros for your
program. The @code{aclocal} program lets you put your own macros into
@file{acinclude.m4}, so simply rename and then run:
@file{configure.in}:
@example
-...
+@dots{}
case $host in
*linux*) HELLO_SYSTEM='hello-linux.$(OBJEXT)' ;;
*) HELLO_SYSTEM='hello-generic.$(OBJEXT)' ;;
esac
AC_SUBST([HELLO_SYSTEM])
-...
+@dots{}
@end example
In this case, @code{HELLO_SYSTEM} should be replaced by
to also use the value of @samp{AM_CFLAGS}, you would need to write:
@example
-maude_CFLAGS = ... your flags ... $(AM_CFLAGS)
+maude_CFLAGS = @dots{} your flags @dots{} $(AM_CFLAGS)
@end example
@item maude_DEPENDENCIES
should include at least all @strong{documented} variables and targets
that a @samp{Makefile.am} authors can use, the behaviours associated to
them (e.g. the places where @samp{-hook}'s are run), the command line
-interface of @samp{automake} and @samp{aclocal}, ...
+interface of @samp{automake} and @samp{aclocal}, @dots{}
@heading What is not in the API