Re: [Omniprint-developer] configure.ac patch

[Oswald B. <os...@kd...>]

On Tue, Jan 06, 2004 at 05:46:08PM -0600, Mark Hamzy wrote:
> Why did you change AC_OUTPUT to AC_CONFIG_FILES?
>
because multiple AC_OUTPUT use is a Bad Hack (TM) and will work only
with some autoconf versions.
info autoconf
sAC_CONFIG_FILES

> It will no longer work as it does generate the Makefiles anymore.
>
bah, i mixed up the obsolete syntax with the current one. move the
config files out of the AC_OUTPUT statement into a separate
AC_CONFIG_FILES, so that AC_OUTPUT is the last command and has no
arguments.

> Also which autogenerated files are safe to remove?
> 
_all_ autogenerated (= derived) files. in particular, anything from the
autotools:
config.guess
config.h.in
config.sub
configure
depcomp
install-sh
ltmain.sh
missing
mkinstalldirs
*/Makefile.in

you can get rid of the dummy docs AUTHORS, COPYING, INSTALL, NEWS,
ChangeLog by adding --foreign to the automake command line or
AUTOMAKE_OPTIONS = foreign to the top-level Makefile.am. the README
should stay in place, i guess.

provide some bootstrap script (autogen.sh is the conventional name) for
cvs users. it probably doesn't need to call anything more than
autoreconf these days.

greetings

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.