summaryrefslogtreecommitdiffstats
path: root/src/build.cc
diff options
context:
space:
mode:
authorEvan Martin <martine@danga.com>2013-02-17 23:13:35 (GMT)
committerEvan Martin <martine@danga.com>2013-04-08 22:02:32 (GMT)
commit149e8d8d5d2b043fa53f9f8b74fff893ea1819df (patch)
tree93c41d13b33be468c61f586f1c25fe637341e29a /src/build.cc
parent5031940a8fa5c0c7a76a4bb7fffdb4526713ce7c (diff)
downloadNinja-149e8d8d5d2b043fa53f9f8b74fff893ea1819df.zip
Ninja-149e8d8d5d2b043fa53f9f8b74fff893ea1819df.tar.gz
Ninja-149e8d8d5d2b043fa53f9f8b74fff893ea1819df.tar.bz2
use logged deps mtime in dirty calculation
The idea here is that it's possible for a build to complete (writing its output) but then for Ninja to get interrupted before writing out the updated dependency information. In that case the mtime stored in the deps log (if any) will match the previous output, and we'll know we need to rebuild the output just to get the deps updated.
Diffstat (limited to 'src/build.cc')
-rw-r--r--src/build.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/build.cc b/src/build.cc
index df208af..ecde4df 100644
--- a/src/build.cc
+++ b/src/build.cc
@@ -516,7 +516,7 @@ void Plan::CleanNode(DependencyScan* scan, Node* node) {
if (!(*ni)->dirty())
continue;
- if (scan->RecomputeOutputDirty(*ei, most_recent_input,
+ if (scan->RecomputeOutputDirty(*ei, most_recent_input, 0,
command, *ni)) {
(*ni)->MarkDirty();
all_outputs_clean = false;