Check that Module.asm in fact exists after the *.asm.js script is run (can add debug logging inside it). The code in that script should set it. But perhaps the script is executed too late, for example.
On Wed, May 18, 2016 at 11:09 PM, awt <[email protected]> wrote: > I am on 1.36.3. I got the error 'Module.asm cannot be found' or something > similar even after I had loaded the xxx_asm.js file in the html before > starting the web worker. Perhaps I'm missing something here? > > On Thursday, May 19, 2016 at 2:10:30 AM UTC+8, Alon Zakai wrote: >> >> This should work. Which version are you on? >> >> On Wed, May 18, 2016 at 9:01 AM, awt <[email protected]> wrote: >> >>> Hi, >>> >>> I was trying to use --separate-asm with proxy-to-worker when I realized >>> that we cannot get the xxx_asm.js file to be loaded in the worker.js? Is >>> there a way around it? Thanks. >>> >>> -- >>> 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. > -- 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.
