diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-10-20 22:59:36 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-10-20 22:59:36 -0700 |
commit | 20037b7c6d510d9f64984db4c51bfe893f7e3e33 (patch) | |
tree | 98fdef84e23d0f8d123393943cccd380948b5357 /053recipe_header.cc | |
parent | 9397c4c26bd2b57bd40bc0a7be22d687dbc96376 (diff) | |
download | mu-20037b7c6d510d9f64984db4c51bfe893f7e3e33.tar.gz |
3534
Streamline the build process. It's safest to always: a) check if each output is `older_than` the inputs necessary to construct it, and b) update the output only if something changed. However: i) We don't yet have helpers to do b) in all situations, and ii) combining a) and b) can cause `older_than` to spuriously report files being updated. So we'll always run exactly one of a) and b) and err on the side of keeping the output reliable, at the risk of occasionally updating a file unnecessarily and triggering unnecessary work downstream. Cross that bridge when we run into it.
Diffstat (limited to '053recipe_header.cc')
0 files changed, 0 insertions, 0 deletions