[Scons-users] Python Logging?

[Bill Deegan]

Nick,

--debug-explain is the place to start.

And for more detail the "--taskmastertrace=FILE" option will yield pretty
(and very verbose) extensive detail on build processing.

At present there's not plans to change the logging.
The big projects are:
Python 3.0
Toolchain re-architecting


-Bill


On Sat, Aug 30, 2014 at 1:46 PM, Vasily <vasslitvinov at pisem.net> wrote:

> 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
>>
>>
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> http://four.pairlist.net/mailman/listinfo/scons-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://four.pairlist.net/pipermail/scons-users/attachments/20140830/f9da96f3/attachment.html>