I apologize for the delayed response. Thanks for the help, Charles! From your suggestion, I managed to find another flag --emit-symbol-map which gave me an fully optimized output with a symbol map mapping the minified functions to the mangled names. This was the closest I have been till date.
This works for me to a certain extend. However, I am still looking for the ideal situation where I can get the fully optimized output together with the sourcemap of my codes. Nevertheless, once again, thank you for your suggestion! On Friday, 24 February 2017 03:04:54 UTC+8, Charles Vaughn wrote: > > Try the --profiling-funcs flag with emcc. The output is still optimized, > but with original mangled function names. I believe Firefox will show > demangled names in its devtools. > > On Thursday, February 23, 2017 at 7:37:25 AM UTC-8, Benjamin Ling wrote: >> >> I notice that during build, my output folder has a ".orig.js" file first >> before finally optimizing it to the final js output. >> >> I have 2 questions around this: >> >> 1) May I know what compilation flag generates this orig.js file? >> >> 2) Is there a way to generate some kind of map of the functions from the >> mangled ones in orig.js to the minified ones in the final js file? >> I understand that we can generate a source map during compilation via the >> -g4 flag. >> But doing this will require exposing some of the debugging information >> and will hence bloat the final output file to around 4x of the output >> wihout the -g flag. >> >> >> -- 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.
