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

From: John Maddock (john_at_[hidden])
Date: 2007-11-21 04:44:13

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.

There are some (undocumented) Boost.Build options you could use as well, but 
the header approach is easier and will work with other tools besides bjam 
that scan dependencies the same way.

HTH, John.