From 9bd1a1619e282c585b3f202d84790f8811d1e4d6 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 10 Apr 2019 14:16:21 +0200 Subject: Always use cached mtime if available Besides other things, this is required for "logical clean" in the try-run mode to work properly: $ b -vn clean update --- build2/context.hxx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'build2/context.hxx') diff --git a/build2/context.hxx b/build2/context.hxx index a8d6833..5799eef 100644 --- a/build2/context.hxx +++ b/build2/context.hxx @@ -420,7 +420,9 @@ namespace build2 // Note that for this mode to function properly we have to use fake mtimes. // Specifically, a rule that pretends to update a target must set its mtime // to system_clock::now() and everyone else must use this cached value. In - // other words, there should be no mtime re-query from the filesystem. + // other words, there should be no mtime re-query from the filesystem. The + // same is required for "logical clean" (i.e., dry-run 'clean update' in + // order to see all the command lines). // // At first, it may seem like we should also "dry-run" changes to depdb. But // that would be both problematic (some rules update it in apply() during -- cgit v1.1