Thanks for the reply! I ended up just sticking with `apt-get install
emscripten`, but I'm going to revisit the vagrant install again later this
week. I'll try the -j1 option, or just install on my main laptop (or maybe
an old box). I was hoping to get a version that was self contained in a
vm, so it's easier to reproduce my builds.
I almost abandoned this again, b/c the emscripten lib I compiled is still
running too slow to be useable (the way I wanted). That could be due to
the way I'm compiling it though. The lib is a command-line app, and deals
with large audio files. When I pass small files, performance is okay, but
it really slows down when I start passing larger files. I'm hoping it's
due to the way I'm compiling, and that there are configure options I can
pass to make the .js code more performant.
Thanks again for the response.
On Monday, December 14, 2015 at 11:59:14 AM UTC-5, jj wrote:
>
> Try clearing the install, and redoing it again, this time capturing the
> log output to check for errors. I believe it had run out of memory again,
> given that the executables don't exist.
>
> Note that emsdk has a number of cores configure option ("-j1") that you
> can pass to the build to make it only use a single core, which will reduce
> memory pressure.
>
>
>
--
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.
