This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
I've been fiddling around a bit with the GTK+ and GLIB trees, and at a
first glance, I like the way they handle rebuilding Makefile.in,
configure, and such with an `autogen.sh' script.
How would folks feel about switching Guile to this system? Among
folks who have used both Guile's way and GTK+'s way, which do you
prefer?
It doesn't have much effect on people building Guile from releases; it
only affects people using CVS, or snapshots (which are currently built
directly from CVS).
As I see it, the advantages of autogen.sh are:
- No more generated files in CVS, so:
- no more meaningless conflicts
- no more spurious rebuilds, caused by CVS not preserving the
relative modtimes of configure and configure.in
- shorter download time (the generated files can be kind of big)
- You basically call autogen.sh instead of calling configure, so you
can always be sure you're doing things right.
The disadvantage is:
- Building from CVS or a snapshot would now require autoconf, automake,
and libtool, in addition to GCC and GNU Make, since the files they
generate would no longer be provided in the repository.