On Fri, Aug 28, 2020 at 6:17 AM Prashanth Nethi
wrote:
> Thanks for the information Alon! That is exactly the information I wanted.
> Your theory of deferred memory usage pattern might be the reason for
> browsers reporting used memory differently.
>
> It is unfortunate that we will not be able
Thanks for the information Alon! That is exactly the information I wanted.
Your theory of deferred memory usage pattern might be the reason for
browsers reporting used memory differently.
It is unfortunate that we will not be able to use PThreads in our main Wasm
because of this limitation, as
Already posted a few times but all of them gets deleted automatically.
Testing if this one will remain...
s...@google.com a következőt írta (2020. augusztus 27., csütörtök, 21:23:05
UTC+2):
> This is because emsdk doesn't read the config file at all, it only writes
> it during `activate`.
>
>
Hi Sam,
Thanks for the explanation. Actually, that's what I concluded myself so I
just wrote my own .emscripten config (LLVM_ROOT path above was actually not
correct as I had to point it to the directory where the package manager
installed llvm) and copied it to my home and to the emsdk
I realized in the meantime that LLVM_ROOT was not set correctly as it
should point to the package bin directory of llvm but it does not help as
the config file is simply ignored. So I decided to create my own script
that sets the environment variables via exports and that worked out.
