update build.zig to support zig 0.13.0 #416
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carenas
suggested changes
Jun 8, 2024
| @@ -99,6 +99,6 @@ src/stamp-h1 | |||
| /bazel-* | |||
|
|
|||
| zig-out/ | |||
| zig-cache/ | |||
There was a problem hiding this comment.
can we keep this line so it also works for zig 0.12.x?
FWIW the rest of the changes are compatible zig 0.12.0 or later.
The cache director is now prefixed with a .[0] Also, std.Build.LazyPath has changed, and now the recommended way to create one that is relative to the repo root is via std.Build.path(). [0]: https://ziglang.org/download/0.13.0/release-notes.html#codezig-cachecode-renamed-to-codezig-cachecode
player-two
force-pushed
the
jgriege/zig-0.13.0
branch
from
9397b5c to
d7251e9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The cache director is now prefixed with a .0
Also, std.Build.LazyPath has changed, and now the recommended way to create one that is relative to the repo root is via std.Build.path().