Re: [Boost-build] Boost.Jam problem with dependant includes

From: Fabien Chêne (fabien.chene_at_[hidden])
Date: 2006-09-28 15:00:26

David Abrahams <dave_at_[hidden]> writes:

> fabien.chene_at_[hidden] (Fabien Chêne) writes:
>
>> I think the documentation is not clear enough about this problematic
>> limitation (the problem is the same with classic Jam).
>> Someone to confirm/infirm that ? 
>
> Confirmed.
>
>> If confirmed, is there a workaround ?
>
> You can improve the scanner that looks for header files by adding
> custome regexps to detect your macros

Yes, i saw the exemple given by Rene Rivera (thanks). but for
example, when we want to convert a large GNU make based project into a
Boost.Jam/Build[2] based project, we have to be conscious of the
existence of such « dependant include ». Otherwise, we can be in big
troubles :-(
That's why i would find it comfortable to be warn about such probably
silent miscompilation -- i don't know how, a line command option for
[b]jam ?.

In fact, it is much more simple to find a work-around for « dependant
include » modifying the C/C++ code than modifying Jam rules.
The problem is indeed when converting a project that contains
§16.2.4-include.

>> And i would find it more safe to block the build if an include is not
>> of the form of :
>
> That would make it useless for Boost, unfortunately.

I'm not sure to understand. Did you mean for building Boost libraries ?
(I don't see such « dependant include » in Boost, maybe i'm wrong)

-- 
Fab