Re: [jamboost] header dependency scanning

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-05-05 09:15:30

Hi On Wednesday 04 May 2005 01:04, Alexey Syomichev wrote:
> I believe that header dependency scanning results used to be cached
> between bjam runs. I also remember that at some point the caching was
> disabled because it didn't show any speed advantage over re-scanning.
> Is this really the case for any level of the performance of a file
> system hosting the project?

> I think I might have a case when caching would be beneficial. I have a
> relatively large project living on a relatively slow NFS system. For a
> build started from the root of the project, it takes about 3
> (frustrating) minutes of "...patience..." before the first update
> action command, 

Can you try running

bjam -sHCACHEFILE=cache

twice. The first invocation should create file 'cache' with results of header 
scanning. The second invocation should pick this file. If there's signigicant 
difference for your case, I can enable header caching globally.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2