You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The most common cross-compilation target seems to be wasm32-unknown-unknown and wasm32-wasi. Users have found needing to install a LLVM/clang toolchain that can target wasm32 to be too much of a burden. We should get rid of the requirement to have a C compiler when targeting wasm32-* targets. (Orthogonally, we're working on expanding the functionality that is available for wasm32-* targets, which means that eventually we should have all functionality available without needing a C compiler.)
The text was updated successfully, but these errors were encountered:
In particular, on macOS hosts, a year or two ago, we have found that Apple Clang wasn't able to target wasm32-* targets, so people had to install LLVM Clang instead. Then, people had trouble dealing with both Apple Clang and LLVM Clang being installed at the same time.
The most common cross-compilation target seems to be wasm32-unknown-unknown and wasm32-wasi. Users have found needing to install a LLVM/clang toolchain that can target wasm32 to be too much of a burden. We should get rid of the requirement to have a C compiler when targeting wasm32-* targets. (Orthogonally, we're working on expanding the functionality that is available for wasm32-* targets, which means that eventually we should have all functionality available without needing a C compiler.)
The text was updated successfully, but these errors were encountered: