Re: [Gpaint-develop] configure broken?

[Andy Tai]

Michael, I believe in most projects of today that use
the (GNU autoconf/automake) "configure; make; make
install" sequences for installation, configure is
always a generated file, produced via the script
"autogen.sh." Though we still store the configure
script in CVS so people checking out from CVS do not
need to run autogen.sh. Running autogen.sh is needed
whenever new source files are added that requires
Makefile.am or configure.in modifications.  Typical
GNOME applications are built like this.

As far as I know, only running autogen.sh is necessary
to generate up-to-date configure.  No need to run
configure beforehand and config.status afterwards. 
Thus this sequence should work:

./autogen.sh
./configure 
make

If this does not work, something is broken:-( 

I learned these by looking at other GNOME applications
and glade output.  All the autoconf/automake stuff is
like black art, so I may not be totally correct.  Let
me know if something does not work according to the
above. Thanks,

Andy


--- "Michael A. Meffie III" <address@hidden>
wrote:
> Andy,
> 
> I removed the generated Makefiles from the
> gnome-1-develop branch.
> These files are supposed to be generated by the
> configure script
> from the Makefile.am file.  For some reason (I
> haven't
> investigated yet) the configure script does not
> generate the
> Makefile.in and Makefile.  To do a clean build, I
> have to run the
> following:
> 
>      $ ./configure
>      $ ./autogen.sh
>      $ ./config.status
>      $ make
> 
> Why do I have to run autogen.sh and config.status?
> 
> -- 
> Michael A. Meffie III           
> http://home.neo.rr.com/meffie/
> 
> 
> _______________________________________________
> Gpaint-develop mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gpaint-develop