Skip to content
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

Tracking issue for wasm-unknown-unknown #178

Closed
carols10cents opened this issue Jun 14, 2019 · 1 comment
Closed

Tracking issue for wasm-unknown-unknown #178

carols10cents opened this issue Jun 14, 2019 · 1 comment

Comments

@carols10cents
Copy link
Member

Not sure about Rust issue, maybe rust-lang/rust#44839 ?

Places that need to be updated:

However, in the meantime, Rust has also grown its own support, independent from Emscripten. This is known as "the unknown target", because instead of wasm32-unknown-emscripten, it's wasm32-unknown-unknown. This will be the preferred target to use once it's ready, but for now, it's really only well-supported in nightly.

@ehuss
Copy link
Contributor

ehuss commented May 25, 2021

Closing per #232, this section has been removed. Indeed there isn't great documentation for targets. Ideally I think that should live in the rustc book, and is something that has been on my todo list to get started for a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants