Hi everyone, it's been a while since Emscripten development has migrated over to the Clang-based "fastcomp" backend, and now it's time for the first Emscripten SDK release that comes with the fastcomp backend default-on. Find the download links from the usual place at https://github.com/kripken/emscripten/wiki/Emscripten-SDK .
There are lots of updates to the Emscripten compiler itself, most notably compilation speed should be much better with the new Clang backend, compared to the old 1.12.0 SDK release. The more complete list of changes in the compiler can be viewed here: https://github.com/kripken/emscripten/blob/incoming/ChangeLog There are also updates to the SDK itself. A notable one is that the SpiderMonkey JavaScript shell is now available with emsdk, type 'emsdk list' to find the package and 'emsdk install spidermonkey-xxx' to install. There are two builds of SpiderMonkey available, a stable and a recent nightly. The advantage of using SpiderMonkey is that it gives a performance boost from excellent asm.js compilation support. Another update is that 32-bit version of the SDK is no longer being updated for Windows. The existing 32-bit toolchains are still there, but new Emscripten SDK updates will only come with the 64-bit version of the Clang compiler. Accordingly, the vs-tool plugin has been updated to work with 64-bit Emscripten SDK - please do report any bugs that you might find there. As a functional change in emsdk, it was requested that the command 'emsdk activate' on Windows would perform permanent registration of environment variables to set up the desired tools without extra steps. As a result, when you now do 'emsdk activate', the Windows UAC elevation prompt might show up to ask for a permission to set environment variables. When installing the new Emscripten SDK via NSIS, it is best to remove any old SDK versions first that were installed via NSIS (Control Panel -> Uninstall a Program), unless you install on top of the exact same directory that you previously installed to. Of course, existing emsdk installations can use the command line emsdk update emsdk install latest-64bit emsdk activate latest-64bit commands to download and install the new version. Also, if you have been manually building fastcomp clang, and have set up environment variables/PATH yourself, you might want to check that there are no duplicate conflicting paths in PATH when you plan to migrate - emsdk will not touch any paths you added manually to PATH. Let us know of any bugs that come up, either here at emscripten-discuss, or one of the bug trackers: - emscripten: https://github.com/kripken/emscripten/issues - emsdk: https://github.com/juj/emsdk/issues - vs-tool: https://github.com/juj/vs-tool/issues Best, Jukka -- 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.
