Seems that all I needed to get things working was 2 more commands: emsdk install --vs2015 emscripten-incoming-64bit emsdk activate --vs2015 emscripten-incoming-64bit
Now, it's time to play with WebAssemblies! :-) Boris On Wednesday, June 22, 2016 at 8:29:46 AM UTC-6, Boris Sergeev wrote: > > Try "emsdk activate --vs2015 sdk-incoming-64bit", does that work? >> > It went a little further and found CLang, but there are still 3 errors: > The SDK/tool 'java-7.45-64bit' cannot be activated since it is not > installed! Skipping this tool... > The SDK/tool 'emscripten-incoming-64bit' cannot be activated since it is > not installed! Skipping this tool... > The SDK/tool 'sdk-incoming-64bit' cannot be activated since it is not > installed! Skipping this tool... > > In Emscripten configuration file, LLVM_ROOT points to the new CLang > binaries, but everything else, esp. EMSCRIPTEN_ROOT, is old: > EMSCRIPTEN_ROOT='C:/Util/Emscripten/emscripten/1.35.0' > > LLVM_ROOT='C:/Util/Emscripten/clang/fastcomp/build_incoming_vs2015_64/RelWithDebInfo/bin' > > > NODE_JS='C:/Util/Emscripten/node/4.1.1_64bit/bin/node' > > PYTHON='C:/Util/Emscripten/python/2.7.5.3_64bit/python.exe' > > SPIDERMONKEY_ENGINE = '' > > V8_ENGINE = '' > > TEMP_DIR = ... > > COMPILER_ENGINE = NODE_JS > > JS_ENGINES = [NODE_JS] > > > > Is this the expected behavior, i.e. Emscripten 1.35.0 and incoming are the > same? > > The reason I need incoming is to try WebAssemblies. > > Thank you, > Boris > -- 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.
