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

From: Stefan Seefeld (seefeld_at_[hidden])
Date: 2007-08-06 07:30:10

Ames, Andreas (Andreas) wrote:

>> For most C/C++ code you need system search paths, which depend on the
>> compiler actually used. Finding user-provided headers isn't enough.
> 
> For actual preprocessing, that's true.  I'm not sure, you really want
> system headers in the list of implicit dependencies (and that means,
> I'm really not sure).

But there is no way of doing real dependency scanning without real
preprocessing. That's the point. Whether you throw away the dependencies
you consider stable is another matter.

> Anyway, the paths to the system headers are highly platform- and tool-
> dependent (as you have mentioned) and should be communicated through 
> the build environment, IMHO.

That's my point: SCons doesn't have any means to communicate these
to the dependency scanner, so you can't easily plug in your own.

(To get this back on-topic, I wonder whether boost.build has any means
to communicate such variables to its own dependency scanner, i.e. how
complicated it would be to hook a boost.wave-based preprocessor up with it.)

Regards,
                Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...