[Freeciv-Dev] Re: having to rerun auto* (was: Compiling latest CVS)

[Jason Dorje Short <vze2zq63@xxxxxxxxxxx>]

Raimar Falke wrote:
> 
> On Fri, Oct 26, 2001 at 11:44:38AM +0200, Reinier Post wrote:
> > On Fri, Oct 26, 2001 at 10:33:20AM +0200, Daniel Sjölie wrote:
> > > On 2001-10-26 10:28:42, Pieter J. Kersten wrote:
> > > > Hello all,
> > > >
> > > > It seems that after the latest city dialog patch the CVS code no longer
> > > > compiles cleanly. It bails out with:
> > >
> > > Run "automake; autoconf; ./configure" (or similar)
> > >
> > > I suppose this will be done and the resulting changes commited to cvs
> > > soon...
> 
> As said before my automake/autoconf changes to much in the files. So
> I depend on other person to do this.
> 
> > Would it be possible to do this automatically?
> 
> I had the remove the Makefile.in changes by hand!
> 
> > Either before code is checked in, or in the make process?

It is possible to do this "automatically":

- Remove all Makefile.in files and configure.  Add these to .cvsignore.

- Create an "autogen.sh" file that runs automake+autoconf+configure. 
This then gets run in place of configure.

The advantage here is that CVS is cleaner (making cvs diffs easier when
you change file structure) and automake/autoconf updates happen
automatically (you have to run configure anyway to get new Makefiles). 
The only disadvantage I know of is that you'll have to have automake and
autoconf installed to be able to compile CVS freeciv (a "make dist"
builds the extra files, so it's not a concern there).  In projects where
I've used this system, I have much preferred it.


The other option as I see it is just to run automake/autoconf
willy-nilly and accept all the spurious changes.  These files aren't an
important part of the cvs tree anyway, so it shouldn't really be a
problem.

jason