Add support for compiling to wasm32 architecture #61
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
lulf
requested review from
thomastaylor312,
bacongobbler and
flavio
as code owners
Signed-off-by: Ulf Lilleengen <lulf@redhat.com>
flavio
approved these changes
Jan 25, 2023
thomastaylor312
approved these changes
Jan 26, 2023
thomastaylor312
added a commit
that referenced
this pull request
Mar 2, 2023
Add support for compiling to wasm32 architecture
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.
Most of the dependencies like reqwest already handle compilation for wasm32, so it is a matter of setting only the supported tokio features and guard some of the reqwest APIs that are not supported on wasm32.
The underlying motivation is to use sigstore on wasm32 architectures, but being able to work with OCI registries from WASM modules might come in handy as well.