-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
zig build: allow to choose "lazy mode" for fetching process #19975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or 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
cd1b1ef
to
76f5b86
Compare
4 tasks
76f5b86
to
66f960a
Compare
d4c0a2b
to
6acd830
Compare
f39a594
to
1857706
Compare
8841db9
to
4024f86
Compare
4024f86
to
a1a68d0
Compare
a1a68d0
to
e76c3bd
Compare
aarch64-linux-release failure seems unrelated |
Yeah, sorry, that's not your fault -- we're seeing a lot of sporadic CI failures now (see this). I'll re-run the failed job. |
fb56ae8
to
275088b
Compare
alexrp
approved these changes
Mar 26, 2025
alexrp
reviewed
Mar 26, 2025
`--fetch` flag now has additional optional parameter, which specifies how lazy dependencies should be fetched: * `needed` — lazy dependencies are fetched only if they are required for current build configuration to work. Default and works same as old `--fetch` flag. * `all` — lazy dependencies are always fetched. If `--system` flag is used after that, it's guaranteed that **any** build configuration will not require additional download of dependencies during build. Helpful for distro packagers and CI systems: https://www.github.com/ziglang/zig/issues/14597#issuecomment-1426827495 If none is passed, behaviour is same as if `needed` was passed. Signed-off-by: Eric Joldasov <[email protected]>
275088b
to
cdf860c
Compare
alexrp
approved these changes
Mar 26, 2025
Thank you |
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.
--fetch
flag now has additional optional parameter, which specifies how lazy dependencies should be fetched:needed
— lazy dependencies are fetched only if they are required for current build configuration to work. Default and works same as old--fetch
flag.all
— lazy dependencies are always fetched. If--system
flag is used after that, it's guaranteed that any build configuration will not require additional download of dependencies during build. Helpful for distro packagers and CI systems: ability to fetch only needed dependencies #14597 (comment)If none is passed, behaviour is same as if
needed
was passed.