| commit | 04d886b11041bb59d01df794cce7a1e8cad2250d | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu May 18 17:34:51 2017 -0700 |
| committer | Colin Cross <ccross@android.com> | Mon May 22 11:29:06 2017 -0700 |
| tree | e56630542064e75e205e85bd97dfd4f6fc693bcd | |
| parent | a127dda3ee92916ef459b3da7aa9f2920ff1a5ab [diff] |
Always rebuild on errors https://groups.google.com/forum/#!msg/ninja-build/YQuGNrECI-4/ti-lAs9SPv8J discusses a case where an rule updates its output file and then fails. The next run of ninja considers the ouptut file clean and doesn't rebuild it. Always stat output files after they are built, and write the mtime into .ninja_log. Consider output files dirty if the recorded mtime is older than the most recent input file.