Binaryen moving away from `-sSINGLE_FILE` by default

[sbc100]

See WebAssembly/binaryen#7985

I'm guessing that binaryen.js wants to ship a single file without a .wasm on the side? But maybe not in all cases?

It looks like you already specify -sSINGLE_FILE in your CI so maybe there is nothing to do here?

binaryen.js/.github/workflows/build.yml

Line 19 in ccf7d1e

CMAKE_EXE_LINKER_FLAGS: "-sMAXIMUM_MEMORY=4294967296 -sSINGLE_FILE"

You could switch that to -DEMSCRIPTEN_ENABLE_SINGLE_FILE but I don't know if make much odds.

This is mostly and FYI bug, feel free to close if there is no action needed at this end.

[CountBleck]

It depends on how Emscripten fetches the Wasm module; if removing -sSINGLE_FILE doesn't play well with bundlers, it might be better to keep it there (I am assuming the generated code works fine for Node.js and such). I need to look into this more.

Tangent: -sSINGLE_FILE_BINARY_ENCODE (if it's not already enabled through the default Emscripten options) might be of interest if we need to stay with -sSINGLE_FILE.

[sbc100]

(-sSINGLE_FILE_BINARY_ENCODE is enabled by default but yes it will help with all users of -sSINGLE_FILE)