-
Notifications
You must be signed in to change notification settings - Fork 57
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
Target wasm32-wasi by default #48
Comments
Out of curiosity, is anybody working on this already, or is preview2 still too far out for that to make sense yet? |
See rust-lang/compiler-team#594 which was just posted 😃 |
Oooh, that is exciting! |
This commit makes `cargo component` target `wasm32-wasi` by default, using a local preview1 adapter to adapter to a preview2 version of WASI. Closes bytecodealliance#48.
This commit makes `cargo component` target `wasm32-wasi` by default, using a local preview1 adapter to adapter to a preview2 version of WASI. Closes bytecodealliance#48.
This commit makes `cargo component` target `wasm32-wasi` by default, using a local preview1 adapter to adapt to a preview2 version of WASI. Closes bytecodealliance#48.
This commit makes `cargo component` target `wasm32-wasi` by default, using a local preview1 adapter to adapt to a preview2 version of WASI. Closes bytecodealliance#48.
* Add preview1 adapter module. The release version is `0c6290c0613e68188e0476cef6c23874528acd81`. * Target `wasm32-wasi` by default. This commit makes `cargo component` target `wasm32-wasi` by default, using a local preview1 adapter to adapt to a preview2 version of WASI. Closes #48.
We should switch from targeting
wasm32-unknown-unknown
and targetwasm32-wasi
by default and automatically link in an adapter for users (at least until preview2 is supported natively in the rust toolchain).The text was updated successfully, but these errors were encountered: