Best way is to use your own HTML shell file and put your own paths in 
there, for example like this:

https://github.com/floooh/oryol/blob/master/web/wasm.html#L30

This doesn't change the location of the wasm file, but its file extensions 
(to .wasm.txt because .wasm files are not compressed by the github pages 
web servers, but .txt files are, some with the .mem file).

The file is actually a python template file, the ${name} part would be 
replaced with the actual app name.

Use the --shell-file linker argument to link with such a custom html shell 
file (see here and search for 
"--shell-file": 
https://kripken.github.io/emscripten-site/docs/tools_reference/emcc.html)

Check the browser dev tools with this live demo to see how it works in the 
end: http://floooh.github.io/oryol/wasm/Clear.html

Cheers,
-Floh.

Am Samstag, 9. September 2017 23:34:34 UTC+8 schrieb ilia.g...@gmail.com:
>
> Hi,
> I am compiling my project to WASM code with JS glue and put them on server 
> side.
> Then I have to load them from server and use.
> Is it possible to control  path to wasm file from JS glue during 
> compilation? Perhaps there are some flags or something else.
> I did not find this option in documentation. I use web workers and lots of 
> API calls, so I am not sure that I it would be easy to load WASM files 
> manually instead of using JS glue code.
>

-- 
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 emscripten-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to