Hi all,
We had the same problems, so for the (re)bootstrapping of our project we now use our own 'bootstrap' script (which is included in both CVS and the source package):
--- #!/bin/sh
echo "---removing generated files---"
# products from ./configure and make
if test -f Makefile ; then
# touch all automatically generated targets that we do not want to rebuild
touch aclocal.m4
touch configure
touch Makefile.in
touch config.status
touch Makefile
# make maintainer-clean
make -k maintainer-clean
fi
# products from autoreconf rm -Rf autom4te.cache rm -f Makefile.in aclocal.m4 compile config.guess config.sub configure \ config.h.in depcomp install-sh ltmain.sh missing py-compile ylwrap
if test "$1" != "clean" ; then # bootstrap echo "---autoreconf---" autoreconf -v -i -f fi ---
Feel free to use this as a template for your own project(s).
Best regards, Sander Niemeijer
On donderdag, dec 2, 2004, at 10:31 Europe/Amsterdam, Eric PAIRE wrote:
Bob Friesenhahn wrote:
I tried this command, but it does not clean up all configure, stamp*, aclocal.m4, ... that was generated by the autotools.On Wed, 1 Dec 2004, Eric PAIRE wrote:
It this solution is so obvious, I don't understand why autotools developers have not already set up a tool which automatically removes the files generated by the autotools (perhaps this tool exists and I don't know about).
It is called 'make maintainer-clean'. Unfortunately, if time stamps are wrong, the Makefile may try to rebuild itself before executing the target.
I guess that these must be removed by hand (or better ignored in the versioning system, if it is possible to get an
exhausitve list of files generated).
Eric
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf