Thank you for the reference to the bug tracker and the potential fix! I 
will try to patch fastcomp as described and then check if this fixes my 
problem!

Best regards,
Björn

Am Donnerstag, 21. April 2016 20:58:16 UTC+2 schrieb Alon Zakai:
>
> This might be
>
> https://github.com/kripken/emscripten/issues/2970
>
> If not, we have a bunch of other source maps issues open - we need more 
> help there.
>
> On Thu, Apr 21, 2016 at 7:34 AM, 'Björn K.' via emscripten-discuss <
> [email protected] <javascript:>> wrote:
>
>> Hi there!
>>
>> I've the following scenario:
>>
>> 1) a C library which is compiled in directory a
>> 2) a C++ class which uses the library and exposes it's functionality via 
>> embind
>>
>> The library is built via a very simple makefile which ensures -g4 als 
>> emcc option. The C++ class is compiled with -g4 as well.
>>
>> In the end I get the following error message when compiling the C++ class 
>> to :JavaScript:
>> sourcemapper: Unable to find original file for mean.c at /home/.../source
>> /emscripten-tests/sourcemap-test-01/mean.c
>>
>> Since it were very helpful to debug the behaviour of 3rd party libraries 
>> which are used in my project I'd really enjoy this working...
>>
>> For reproduction I've put the simple project online here:
>> https://github.com/cee-dee/emscripten-tests/tree/master/sourcemap-test-01
>> Note: When putting the sourcecode of the library into the same directory 
>> as the C++ class everything works fine.
>>
>> Anyone here who can help me out?
>>
>> Best regards,
>> Björn
>>
>> -- 
>> 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] <javascript:>.
>> 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.

Reply via email to