So, spurious changes (touching a file) will result in a cache hit, while hidden changes (changing an environment flag used by Make) are caught.
This is particularly important if verifiable builds are needed for SoX compliance.
So, spurious changes (touching a file) will result in a cache hit, while hidden changes (changing an environment flag used by Make) are caught.
This is particularly important if verifiable builds are needed for SoX compliance.
https://github.com/bazelbuild/bazel/blob/34ce6a23f5a2be58bb5...
I don't know enough about bazel to answer your question definitively, but "stamping" is what you want to search for.
It checksums the preprocessed files, so neither `__DATE__`, no comment changes should affect your build times.
The .a/.so/.exe would no longer match the inputs (the .o files), causing a re-link.
Bazel can also read source file hashes from the filesystem if the filesystem supports it.