I tried deleting those folders. They get recreated then. Looks like juj merged the pull request already so it should be available in future releases.
On Tuesday, October 6, 2015 at 9:45:41 PM UTC+2, Robert Goulet wrote: > > Did you try on a different machine that never had Emscripten, and without > the .emscripten_cache and .tmp folders created? I had some issues with that > too. > > On Tuesday, October 6, 2015 at 1:26:11 PM UTC-4, Markus Henschel wrote: >> >> This might be a bit late but I just ran into the same issue. I created a >> pull request with a solution. >> https://github.com/juj/emsdk/pull/40 >> >> On Wednesday, August 26, 2015 at 10:50:41 PM UTC+2, Robert Goulet wrote: >>> >>> Hi, I'm trying to get Emscripten to be used on multiple system, which >>> might be installed at different locations. Using the emsdk activate >>> --embedded still generates a .emscripten file that contains absolute >>> paths. Is there a way to work-around this so that these paths refer to the >>> directory the .emscripten file currently resides? That way we could >>> completely avoid calling emsdk activate on new build machines. >>> Suggestions? >>> >>> Thank you. >>> >> -- 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.
