From f6027721b125af34862d1ba7ca5ba2205a09e1fe Mon Sep 17 00:00:00 2001 From: Gary Oberbrunner Date: Tue, 1 Mar 2011 00:48:34 +0000 Subject: New debug option --debug=prepare to watch targets being prepared --- doc/man/scons.1 | 12 ++++++++++++ doc/user/troubleshoot.in | 15 +++++++++++++++ doc/user/troubleshoot.xml | 15 +++++++++++++++ src/CHANGES.txt | 4 ++++ src/RELEASE.txt | 5 ++++- src/engine/SCons/Script/Main.py | 2 ++ src/engine/SCons/Script/SConsOptions.py | 2 +- src/engine/SCons/Taskmaster.py | 8 ++++++++ 8 files changed, 61 insertions(+), 2 deletions(-) diff --git a/doc/man/scons.1 b/doc/man/scons.1 index 5d3cfd9..3fa9e0c 100644 --- a/doc/man/scons.1 +++ b/doc/man/scons.1 @@ -664,6 +664,18 @@ Re-run SCons under the control of the Python debugger. .TP +--debug=prepare +Print a line each time any target (internal or external) +is prepared for building. +.B scons +prints this for each target it considers, even if that +target is up to date (see also --debug=explain). +This can help debug problems with targets that aren't being +built; it shows whether +.B scons +is at least considering them or not. + +.TP --debug=presub Print the raw command line used to build each target before the construction environment variables are substituted. diff --git a/doc/user/troubleshoot.in b/doc/user/troubleshoot.in index 392caf6..b0e8681 100644 --- a/doc/user/troubleshoot.in +++ b/doc/user/troubleshoot.in @@ -842,6 +842,21 @@ +
+ + Watch &SCons; prepare targets for building: the &debug-prepare; Option + + + + Sometimes SCons doesn't build the target you want + and it's difficult to figure out why. You can use + the --debug=prepare option + to see all the targets &SCons; is considering, whether + they are already up-to-date or not. The message is + printed before &SCons; decides whether to build the target. + +
+