Basically, just to assign to Module.wasmBinary (see https://kripken.github.io/emscripten-site/docs/api_reference/module.html ).
Here the issue is we need the wasm binary - it's in a side file with suffix .wasm. You can either load it yourself and assign it to Module.wasmBinary, or you can build to HTML, and emcc will do it all for you. On Tue, Nov 1, 2016 at 7:41 PM, Mark Sibly <[email protected]> wrote: > Hi, > > Ok, got my first wasm app built, but when I tried to visit it via browser > I get: > > Assertion failed: on the web, we need the wasm binary to be preloaded and > set on Module['wasmBinary']. emcc.py will do that for you when generating > HTML (but not JS) > > Does this mean I need to --preload-file the output file with the .wasm > extension when linking? > > This I can do, but I'm not sure what 'set on Module['wasmBinary]' involves. > > Bye! > Mark > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
