- 05 Jun, 2015 1 commit
-
-
Kitware Robot authored
-
- 04 Jun, 2015 20 commits
-
-
Brad King authored
-
7657e8b1 cmMakefile: Introduce a local cmMakefile variable. 4e8f242d cmMakefile: Store unconfigured cmMakefiles. d65e0123 cmMakefile: Implement ConfigureSubDirectory in terms of cmMakefile. f059ed16 cmMakefile: Move Configure responsibility from cmLocalGenerator. a653611d cmake: Replace CurrentLocalGenerator concept with CurrentMakefile. 69a038a9 cmMakefile: Refactor directories specified with the subdirs command. 08637970 cmLocalGenerator: ComputeObjectMaxPath just before generating. 27e11c6f Merge Configure state with GeneratingBuildSystem state. 363caa2f cmLocalGenerator: De-virtualize Configure().
-
eb7b6f6d cmVariableWatchCommand: Simplify error reporting. 499ebb65 cmListFileBacktrace: Internalize the step of making paths relative. 80b433b0 cmGlobalGenerator: Don't use else after a return. 52919ac8 cmMakefile: Make cmListFileBacktrace default constructible. b68f2ea8 cmMakefile: Add API for elseif to create backtrace. 17e13f0a cmMakefile: Simplify CMP0000 handling.
-
c85367f4 VS: Compute project GUIDs deterministically
-
-
Not cmLocalGenerators.
-
-
The generator should only have a function at generate time.
-
-
Store the directories on the cmMakefile as explicitly not-configured-yet.
-
-
-
The generators that override it do so in order to populate data members which can instead be populated in Generate().
-
Port callers away from it.
-
Brad King authored
Compute deterministic GUIDs that are unique to the build tree by hashing the path to the build tree with the GUID logical name. Avoid storing them in the cache, but honor any found there. This will allow project GUIDs to be reproduced in a fresh build tree so long as its path is the same as the original, which may be useful for incremental builds.
-
Kitware Robot authored
-
- 03 Jun, 2015 8 commits
-
-
-
-
The test for this variable was removed in commit v2.8.8~330^2~7 (complex: Remove ancient unused ComplexRelativePaths test, 2011-12-23). Commit v3.1.0-rc1~425^2~2 (backtrace: Convert to local paths in IssueMessage, 2014-03-12) appears to have accidentally made some backtraces print relative paths with the variable because conversions which used to be done at configure time, before the variable had an effect are now potentially done at generate time. The documentation of the variable says not to use it, and the docs are wrong in that the variable actually applies in per-directory scope. The read of the variable makes it harder to split conversion methods from cmLocalGenerator where they don't belong. Remove it now.
-
Brad King authored
-
Brad King authored
Check for this flag explicitly in the --help output before using it. It turns out there are some versions of the tool that support --version but not --ignore-missing-info.
-
Brad King authored
Use if(MATCHES) to verify that a match exists before using the match group variable.
-
Brad King authored
Use the KWSys Process "MergeOutput" option to give each test child process the same pipe for both stdout and stderr. This allows natural merging of stdout and stderr together instead of merging on arbitrary buffered read boundaries as before.
-
Kitware Robot authored
-
- 02 Jun, 2015 11 commits
-
-
Stephen Kelly authored
Leave the namespace open for other Parent types.
-
Stephen Kelly authored
Leave the namespace open for other snapshot types.
-
Stephen Kelly authored
-
Stephen Kelly authored
-
Stephen Kelly authored
Currently cmMakefile calls MakeRelative on a copy of the backtrace, emits the copy to the stream once, then discards the copy. There is no need to have API for the path conversion.
-
Stephen Kelly authored
-
Stephen Kelly authored
-
Stephen Kelly authored
-
Stephen Kelly authored
-
Brad King authored
-
Brad King authored
-