I tried source maps on my engine, and the generation worked ok. I compile all source files to a few separate .bc files, and then link those together to the final .html and .js files. There were no errors during build and in Firefox the source maps are located properly in the debugger. In Chrome source maps did not work. I was not able to add breakpoints to anywhere in the code, so I was unable to step through. Jez Ng wrote the source mapping support for Emscripten, perhaps he knows more about the current limitations.
2014-07-01 12:23 GMT+03:00 Warren Seine <[email protected]>: > Hi, > > I can generate source maps for my main program, but when linking libraries > generated from different paths, the source mapper can't find the source > files for libraries. The source mapper doesn't allow to specify multiple > look-up paths and even if it did, I'm sure it'd introduce new issues. > > Here are the questions: > > - What's the current status for the Emscripten source mapper? Are > people really able to use it to debug large codebases including libraries? > - Would it be possible to build each source map when building > libraries, and somehow merge them when linking? > - If not, what's the workaround? Using absolute paths when building? > > 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.
