Re: [Boost-build] Dependency scanning bug

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-12-11 14:47:30

On Tuesday 11 December 2007 21:59:08 Vladimir Prus wrote:
> On Monday 10 December 2007 23:03:34 Phillip Seaver wrote:
> > I don't have the latest version of boost-build (looks like I imported it 
> > from the May 15th nightly release), but I couldn't find a similar bug in 
> > the tracker.
> > 
> > One of my co-workers ran into an interesting problem.  He had a 
> > directory named "new" in one of his source directories.  Every time he 
> > modified the "new" directory, it caused most (if not all) of the C++ 
> > files to be rebuilt.  The reason is that it was looking at the timestamp 
> > of the "new" directory (instead of the system "new" include, I believe) 
> > and seeing that it was newer than the object files.
> > 
> > Is it possible/reasonable to exclude directories from dependency scanner 
> > matching?
> 
> Guess it's reasonable, given that gcc ignores directories during
> search for header anyway.
> 
> I think we'd need to add a flag to target saying 'it's file', and if such
> a flag is set, ignore non-files when searching for the target. Rene,
> does this seem reasonable to you?

Actually, we have ISFILE rule, but it has no effect on anything. I've fixed
that and changed Boost.Build to take advantage of this, in revisions
41980 and 41981. Can you grab the SVN version of bjam and boost.build and
see if it fixes the problem for you?

- Volodya