Re: [boost] Release Tools Analysis Part I: Build systems

From: Ames, Andreas (Andreas) (ames_at_[hidden])
Date: 2007-08-06 06:10:15

> -----Original Message-----
> From: boost-bounces_at_[hidden] 
> [mailto:boost-bounces_at_[hidden]] On Behalf Of Hartmut Kaiser
> Sent: Sunday, August 05, 2007 2:17 AM
> To: boost_at_[hidden]
> Subject: Re: [boost] Release Tools Analysis Part I: Build systems
> 
> David Abrahams wrote: 
> 
> > Neither systems can trace #include dependencies through 
> > macros (e.g. #include SOME_MACRO(xyz)), which occasionally 
> > leads to inaccurate results from incremental testing.  This 
> > is an important problem that should be fixed.
> 
> FWIW, Wave can be used to generate a complete list of 
> dependencies (full
> names of included files). This requires knowledge about all predefined
> system dependend macros, though.

Maybe it would be worth then, to make wave the default preprocessor for
boost, i.e. to change the build system to take preprocessed files as the
input to generate object files.  At least this would prevent errors
resulting from the fact that the implicit dependencies are generated 
from another tool (wave) than the compiler's default preprocessor (unless
you think this is a non-issue).

The disadvantages of this approach would be:

* increased compile times

* much more disk storage needed

* precompiled headers would probably no longer be available

cheers,

aa

--
Andreas Ames | Programmer | Comergo GmbH | ames AT avaya DOT com
Sitz der Gesellschaft: Stuttgart
Registergericht: Amtsgericht Stuttgart - HRB 22107
Geschäftsführer: Andreas von Meyer zu Knonow, Udo Bühler, Thomas Kreikemeier