Re: [boost] Forcing rebuild of tests when headers change

From: Paul A Bristow (pbristow_at_[hidden])
Date: 2007-11-21 05:15:17

>-----Original Message-----
>From: boost-bounces_at_[hidden] 
>[mailto:boost-bounces_at_[hidden]] On Behalf Of John Maddock
>Sent: 21 November 2007 09:44
>To: boost_at_[hidden]
>Subject: Re: [boost] Forcing rebuild of tests when headers change
>
>Anthony Williams wrote:
>> It's quite possible that this is because most of the thread headers
>> are platform-dependent, so are included through a macro expansion
>> (e.g. the one in boost/thread/tss.hpp). If so, is there a way to flag
>> the dependency directly?
>
>Exactly, if you include via:
>
>#include SOME_HEADER
>
>then bjam can't trace the dependencies, one trick would be to 
>have a code 
>block:
>
>#if 0
>   // This block is for header dependency scanners:
>#  include <a.hpp>
>#  include <b.hpp>
>#endif
>
>at the end of the header to ensure that the dependencies get tracked 
>correctly.

This may also be most helpful to *human readers* too - who may also find things macroized like this confusing ;-)

So it would be Good Documentation Practice too.

Paul

---
Paul A Bristow
Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB
[phone] & SMS, Mobile [phone] & SMS
pbristow_at_[hidden]