8 Dec
2005
8 Dec
'05
10:38 a.m.
Indeed. One thing I already proposed in the past: some dummy tests (akin to autoconf macros) that make sure a sane configuration / environment is available at all. These tests could cover a specific toolchain, or even some lightweight library-specific code. If these are known as dependencies for the rest of the test suite(s), quite a bit of computing power (and mail bandwidth) could be spared whenever these fail.
Good thinking, all we need is a "hello world" program and make all the tests dependent upon a successful build of that specific program. Adding a hello world program to say Boost.Config is pretty trivial, would someone like to volenteer to hack Boost.Build? John.