Recognize the "wasm32-wasi" target tuple. #402
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.
To minimize confusion with multiarch tuples which omit the vendor field of the target tuple, and to save a small amount of typing, we're preparing to switch the "wasm32-unknown-wasi" target to be spelled "wasm32-wasi". LLVM already accepts both forms. This is similar to how the vendor field is omitted in rustc tuples such as "x86_64-fuchsia" and "aarch64-linux-android".
The patch here just changes the cc-rs crate to recognize either form in anticipation of this change.