I haven't found a workaround yet (besides putting everything is absolute), but I'm still concerned about the issue.
I didn't take the time to make a proper test case though. Since you have reduced the issue to a simple case, maybe you could add a test case about it? On Thursday, August 14, 2014 8:11:19 PM UTC+2, Robert Goulet wrote: > > I have the exact same issue. > > This happens in a relatively simple setup: > > Say you have two projects, one is the executable (html) and the other is a > library (bc). The source code for these two projects reside in different > folders such as this: > > .../root/project1/foo1.cpp > .../root/project2/foo2.cpp > > Assume project1 is the executable target, it links and depends on project2. > > Emscripten source mapper generates the following error with the source > mapper in such a setup: > > *sourcemapper: Unable to find original file for project2/foo2.cpp at > .../root/project1/foo2.cpp* > > Basically, it seems the source mapper assumes the source files will be > located in a relative path to the executable project, when in fact it is in > the same folder as the library project. > > Is there a work-around for this? I tried using absolute paths in the > visual studio project and it didn't work. > > > On Tuesday, July 1, 2014 1:51:59 PM UTC-4, Alon Zakai wrote: >> >> If you build each source file with -g, and build the final linked output >> with -g4, you should get valid source maps, assuming that the source files >> are in the right relative position (as when they were compiled). If that >> doesn't work for you, can you make a testcase showing the issue? >> >> - Alon >> >> >> >> On Tue, Jul 1, 2014 at 2:23 AM, Warren Seine <[email protected]> wrote: >> >>> 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.
