-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
wasmtime: add enableShared/enableStatic & shell completions #440501
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
GaetanLepage
merged 3 commits into
NixOS:master
from
nekowinston:wasmtime/shared-and-static-options
Sep 12, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know if there's a difference between those two in practice? (Does
wasmtime completiondo anything other than cat the completion files?).I'm asking because if not, we could simplify to just run the second option in both cases, when
stdenv.buildPlatform.canExecuteand when it cannot.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So my understanding of this snippet (referenced from tree-sitter's nixpkgs shell completions) is that this is for
pkgsCrosscross compilation. First we needwasmtime completionto put the files under$out/share/{bash,fish,zsh}on our native architecture.Then when building e.g.
pkgsCross.armv7l-hf-multiplatform.wasmtime,buildPackagesrefers to the host architecture; the completions are copied from there to the cross-compilation target, since the build platform can't runwasmtime completionitself if it's targeting armv7.I actually just tried this on my end with
nix-build . -A pkgsCross.armv7l-hf-multiplatform.wasmtimeand have noticed that ourcargoShortTargetis wrong. I think it should bestdenv.hostPlatforminstead ofstdenv.targetPlatform, because the C API headercpfails.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see, thank you. I didn't know this construct; out of interest I tried to use the second option and I run into infinite recursion, so I see now. The solution on this PR is working as expected: