TL;DR: does STANDALONE_WASM=1 imply WASI-required? I've been building my wasm code with STANDALONE_WASM=1. This runs in d8 just fine (though it still requires the .js wrapper to launch), and also in wasm-interp, but only if I build WASI support into wasm-interp (otherwise I'll fail with things like `invalid import "wasi_snapshot_preview1.fd_write"`).
The comments in Emscripten's settings.js regarding STANDALONE_WASM don't seem entirely clear on this front. My assumption at the moment is that STANDALONE_WASM=0 means "You will almost certainly require JS and WASM" (which is fine), but STANDALONE_WASM=1 apparently means "You might require JS and/or WASI in addition to WASM". (The motivation here is that I'd like to use wabt's wasm-interp in a configuration without WASI, but it's not clear to me whether there is a set of flags for Emscripten that will reliably produce standalone wasm that requires neither WASI nor other JS-specific imports from "env".) -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAM%3DdnvfwXFpSG0N%2BfG-Us02bSFASTFeLS_9JewN8S4G5ijreYQ%40mail.gmail.com.
