From: David Abrahams (dave_at_[hidden])
Date: 2004-11-12 21:30:02
"c_andy_martin" <c_andy_martin_at_[hidden]> writes:
> This seems to be a problem with bjam. If you have a directory named
> the same as an include file in your project, when the directory's
> timestamp is changed bjam interprets the include file as being out of
> date. This is a problem, when for instance, you have a directory
> called `utility' that you include files from, and you also make use of
> the STL <utility> header (either directly, or indirectly). See the
> original email below for a detailed example.
> Does anyone familiar with the bjam source no why this is occuring and
> if there are any workarounds? I'm not familiar enough with the bjam
> source to track down where the timestamping is done and why it
> confuses a directory name in one directory with an include file in
> I have tried this with both BBv1 and BBv2 with the exact same results.
I'm familiar enough with the source to know that it shouldn't be
happening. Header and directory targets with the same names should be
gristed to distinguish them from one another. I suggest you do
to see how the targets are getting identified.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk