Okay. Would it make sense to mention this behaviour somewhere in the docs? Maybe here: https://kripken.github.io/emscripten-site/docs/porting/emterpreter.html?highlight=emterpretify#general-usage <https://kripken.github.io/emscripten-site/docs/porting/emterpreter.html?highlight=emterpretify#general-usage> and here: https://kripken.github.io/emscripten-site/docs/tools_reference/emcc.html#emcc-js-opts <https://kripken.github.io/emscripten-site/docs/tools_reference/emcc.html#emcc-js-opts>
I don’t think this is a big issue, but still it can catch you by surprise... > On 03 Jan 2017, at 19:58, Alon Zakai <[email protected]> wrote: > > I see. Ok, then the issue is that js opts are needed for emterpretify. In the > debug output we show "enabling js opts for EMTERPRETIFY" if they were not > enabled already. In other words, emterpretify forces js opts, which affects > minification. -- 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.
