The typical way is to wait for main() to be called. If you app doesn't have a main(), add a tiny one just for the purpose of noticing when it is called, then setting some state saying that it is ok to call compiled code now.
The change you see is likely because we enabled .mem files by default. Perhaps you need to copy that file over alongside your other files? Or is a .mem file not being generated (which would be a bug)? - Alon On Tue, Sep 16, 2014 at 10:44 PM, Richard Bateman <rich...@batemansr.us> wrote: > I just upgraded to 1.22.0 with no other changes and I'm suddenly getting > this message: > > you need to wait for the runtime to be ready (e.g. wait for main() to be > called) > > it's also suddenly trying (badly) to load a non-existant .mem file from > the server; I have not changed any compilation flags from when I was using > 1.21.0. > > Anyone know what might be causing this or how I can prevent it? For that > matter, how does one normally detect whether or not the runtime is ready > and/or wait for it to become ready? > > Thanks! > > Richard > > -- > 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. > -- 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.
