feat: external and persisted Zig cache #253
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Configure an external, globally shared, and persisted cache directory for the Zig compiler. This directly follows the example of uber/hermetic_cc_toolchain.
Closes #87
This is required for Zig 0.12 support as Zig 0.12 produces dangling symlinks in its cache directory, making the current approach of treating the cache directory as a build output infeasible, see bazelbuild/bazel#15454 (comment).
Time saved due to persisted Zig cache