Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Emscripten 1.37.16 to 1.37.36 #37291
Motivation for this change
this extends the PR from #35636 which got reverted and does many cleanups.
Mar 18, 2018
8 checks passed
@Ericson2314 Unfortunately, the wasm backend in LLVM isn't nearly mature enough for most people's use cases. The compiler is fine, but it lacks critical components like libc. I've been getting by without by just porting stuff myself, but it's all very thrown-together and I probably wouldn't recommend it to be anyone's default at the moment. Emscripten is a reasonably production ready toolchain, plus it supports compiling to JS. As much as I dislike Emscripten, I think it'll be here for a while until the wasm story gets more fleshed out as a proper cross target.
That said, I'm not super happy seeing all kinds of special cases for Emscripten in nixpkgs. As a toolchain, Emscripten is really poorly designed.
as long as there is no prototype code or even documentation on how to get rid of emscripten i don't see how that should be done.
emscripten works actually pretty well as a standalone and combined with nixpkgs i think it can be automated even futher. that said, over time we can move away from it but there need to be examples working and i don't see any.
@ElvishJerricco can't find wasm-cross in
in general, don't underestimate the amount of work emscripten does behind the scenes. i've spent at least 3 full weeks (nerd weeks, not employe weeks) in emscripten documentation and examples, talked to several developers while writing
but i've not yet used
I don't. And this is exactly why it's terrible. C toolchains should not have so much work to do. wasm-cross certainly doesn't.