diff options
author | Ben Boeckel <ben.boeckel@kitware.com> | 2015-07-21 21:18:53 (GMT) |
---|---|---|
committer | Ben Boeckel <ben.boeckel@kitware.com> | 2015-07-23 19:33:10 (GMT) |
commit | 594bafe52773c940fc3fb9cd9022a4d1a3a194c7 (patch) | |
tree | 9ba8747bc0a23a46abe7035e8f507b647573fbd9 /Source/cmake.h | |
parent | 265b9db7c2c865c5aad821bf9a377ea84dfe431e (diff) | |
download | CMake-594bafe52773c940fc3fb9cd9022a4d1a3a194c7.zip CMake-594bafe52773c940fc3fb9cd9022a4d1a3a194c7.tar.gz CMake-594bafe52773c940fc3fb9cd9022a4d1a3a194c7.tar.bz2 |
cmake: add --trace-expand option
The --trace option is helpful, but sometimes, what you're looking for is
deep under many layers of function calls and figuring out what instance
of the function call you're looking at is tedious to determine (usually
involving patching and message()). Instead, add a --trace-expand option
to trace while expanding commands into what CMake actually sees.
Diffstat (limited to 'Source/cmake.h')
-rw-r--r-- | Source/cmake.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Source/cmake.h b/Source/cmake.h index f0f9411..20e49e3 100644 --- a/Source/cmake.h +++ b/Source/cmake.h @@ -270,6 +270,8 @@ class cmake // Do we want trace output during the cmake run. bool GetTrace() { return this->Trace;} void SetTrace(bool b) { this->Trace = b;} + bool GetTraceExpand() { return this->TraceExpand;} + void SetTraceExpand(bool b) { this->TraceExpand = b;} bool GetWarnUninitialized() { return this->WarnUninitialized;} void SetWarnUninitialized(bool b) { this->WarnUninitialized = b;} bool GetWarnUnused() { return this->WarnUnused;} @@ -378,6 +380,7 @@ private: WorkingMode CurrentWorkingMode; bool DebugOutput; bool Trace; + bool TraceExpand; bool WarnUninitialized; bool WarnUnused; bool WarnUnusedCli; |