From 5ce1f438decd05e01a16445da4703c2193447428 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 25 Aug 2021 08:13:27 +0200 Subject: Keep mtime check always enabled on Windows Windows is known not to guarantee monotonically increasing mtimes. --- libbuild2/config.hxx.in | 6 ++++-- libbuild2/depdb.hxx | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) (limited to 'libbuild2') diff --git a/libbuild2/config.hxx.in b/libbuild2/config.hxx.in index 59917db..9a2e01f 100644 --- a/libbuild2/config.hxx.in +++ b/libbuild2/config.hxx.in @@ -21,9 +21,11 @@ #define LIBBUILD2_STAGE true // Modification time sanity checks are by default only enabled for the staged -// version but this can be overridden at runtime with --[no-]mtime-check. +// version unless we are on Windows (which is known not to guarantee +// monotonically increasing mtimes). But this can be overridden at runtime +// with --[no-]mtime-check. // -#if LIBBUILD2_STAGE +#if LIBBUILD2_STAGE || defined(_WIN32) # define LIBBUILD2_MTIME_CHECK true #else # define LIBBUILD2_MTIME_CHECK false diff --git a/libbuild2/depdb.hxx b/libbuild2/depdb.hxx index abc2565..671c7fd 100644 --- a/libbuild2/depdb.hxx +++ b/libbuild2/depdb.hxx @@ -128,7 +128,7 @@ namespace build2 // Note that it would also be good to compare the target timestamp against // the newest prerequisite. However, obtaining this information would cost // extra (see execute_prerequisites()). So maybe later, if we get a case - // where this is a problem (in a sense, the database is a buffer between + // where this is a problem (in a sense, the database is a barrier between // prerequisites and the target). // void -- cgit v1.1