configuration lacks (vital) capabilities

[Lars Stavholm <stava@…>]

I haven't found a way to do the following, so I'm just assuming it's not there.

One should really be able to perform something like the following common build steps:

./bootstrap
./configure --prefix=/usr/local
make
cd dox
make
make install
cd ..
make install

I.e.:

• being able to execute local (and to be able to be sure it's local) scripts or programs (the dot slash notation).
• being able to jump to subdirectory for extra make, like dox and such.
• being able to see output (stdout and stderr) from the commands (slave, even in DEBUG mode, only some of the traces shows up, there's some sort of filtering going on there).

The xml notation used by ​Luntbuild is a pretty good (and successful) example (unfortenatly not python, and definitely not integrated with ​trac. A more elaborate, but still very useful example can be seen in ​Test-AutoBuild (this is a perl-ish framework).

[stava@…]

I thought I'd add my 2 cents worth:

We use the same build steps that you describe for most of our builds, and we made the following changes in the build configuration to make it work for us:

1. The dot slash notation replaced with "sh bootstrap" and "sh configure ...".

2. The doc target created in the top level Makefile, so we can do "make doc" which in turn translates into "cd doc" + "make".

Works like a charm.

Cheers /Lars