[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: svn copy conflicts with autotools ?

From: Sander Niemeijer
Subject: Re: svn copy conflicts with autotools ?
Date: Thu, 2 Dec 2004 10:51:13 +0100

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):


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 config.status
  touch Makefile
# make maintainer-clean
  make -k maintainer-clean

# products from autoreconf
rm -Rf autom4te.cache
rm -f aclocal.m4 compile config.guess config.sub configure \ depcomp install-sh missing py-compile ylwrap

if test "$1" != "clean" ; then
  # bootstrap
  echo "---autoreconf---"
  autoreconf -v -i -f

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:

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 tried this command, but it does not clean up all configure, stamp*, aclocal.m4, ... that was generated by the autotools. 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).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]