[Scons-users] debugging why scons is not using the cache?
roundyd at physics.oregonstate.edu
Mon Aug 5 14:51:37 EDT 2013
No, I didn't try that. However, it just says "building `foo.o' because it
I do have some new information: the cache *does* work, it just isn't
working for C++ files. It works fine for haskell files, and a few other
types... but most of my code is C++. This rules out the possibility that
the cache directory simply is not writable.
I have not yet figured out a way to make scons announce when it writes to
the cache, or when it fails to find something in the cache. The
--cache-debug option seems to only have effect for commands for which the
cache works, i.e. it gives extra information for the times when files are
retrieved from cache, but not otherwise.
On Mon, Aug 5, 2013 at 11:26 AM, Bill Deegan <bill at baddogconsulting.com>wrote:
> Have you tried: scons --debug=explain ?
> I think it may "explain" why things are being built or not
> On Mon, Aug 5, 2013 at 11:00 AM, David Roundy <
> roundyd at physics.oregonstate.edu> wrote:
>> I've got
>> CacheDir(os.environ['HOME'] + '/.cache/scons')
>> right at the beginning of my SConstruct file, which works fine on one
>> computer, but on a different computer (with $HOME mounted over nfs,
>> incidentally) I am not getting any caching.
>> Any suggestions as to how I might go about debugging this?
>> Scons-users mailing list
>> Scons-users at scons.org
> Scons-users mailing list
> Scons-users at scons.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scons-users