[Scons-users] Python Logging?

[Nick Hilton]

Yes, I've tried using it but it's not as accurate as I would like.  When using a CacheDir, explain will just say the file doesn't exist and will rebuild it.


I've ran into permissions issues with a shared CacheDir() so explain won't indicate that a cached file exists but can't be read.  It won't tell me that it can't write to the cache either.

I'd like to see some logging that states this level of detail.

Sometimes I'd like this detail for documenting the dependency tree, with details about how a dependency got into the tree in the first place.

:)
Nick



________________________________
From: Vasily <vasslitvinov at pisem.net>
To: Nick Hilton <weegreenblobbie at yahoo.com>; SCons users mailing list <scons-users at scons.org> 
Sent: Saturday, August 30, 2014 1:46 PM
Subject: Re: [Scons-users] Python Logging?



I'm not a really experienced SCons user, but there's an option you might be looking for - "--debug=explain" should tell you why SCons is rebuilding this or that.

Thanks,
Vasily



2014-08-31 0:02 GMT+04:00 Nick Hilton via Scons-users <scons-users at scons.org>:


>
>
>Hello,
>
>
>I would like to lean the structure of scons so I can create fixes for bugs that I find.  However the codebase is pretty complex the last time I tried to follow the execution path.
>
>
>For a project at work, we are using a shared cache dir, yet sometimes I see output like this:
>
>
>    Retrieved some/path/to/target from cache
>    Building some/path/to/target
>
>
>So it pulled the file from cache and then immediately builds it again.
>
>
>Using the the Python logging module might help newbies or veterans alike to understand what's happening under the hood.
>
>
>Are there any plans on using the Python logging module to get detailed debug messages as to why actions are taking place?
>
>
>Thanks!
>Nick
>_______________________________________________
>Scons-users mailing list
>Scons-users at scons.org
>http://four.pairlist.net/mailman/listinfo/scons-users
>
>