I might have missed it then - are there docs about how to do the entire workflow?
- Alon On Tue, Jan 6, 2015 at 4:25 PM, Bruce Mitchener <[email protected]> wrote: > On Wed, Jan 7, 2015 at 4:32 AM, Alon Zakai <[email protected]> wrote: > >> I believe that old way won't work any more, correct. You might be able to >> hack it to, though - need to avoid capturing malloc and free in variables >> in the asm() function. If you use them from the global scope instead, that >> might be fine (but slower). >> >> There is new work to trace malloc and free with the EMSCRIPTEN_TRACING >> flag (grep for it to see usages). But I'm not sure that is ready yet. >> > > It works for me and I've gotten reports from others that it works for them > ... > > - Bruce > > -- > 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.
