Emscripten SDK 1.30.0 release!

330 views
Skip to first unread message

Jukka Jylänki

unread,
Apr 12, 2015, 11:33:26 AM4/12/15
to emscripte...@googlegroups.com
Hi there,

   the Emscripten SDK packages have now received an update to version 1.30.0. This includes the following updates:

  - Emscripten 1.30.0 compiler which is based on Clang 3.5. The previous 1.29.0 release was the only release to be based on Clang 3.4, and likewise this release will be the only one to be based on Clang 3.5, as the next master merge will have Clang 3.6
  - Node.js has been updated to version 0.12.2 from the old 0.10.x versions.
  - Two new SpiderMonkey packages are available, first one is the current stable 37.0.1, and second one is a Nightly snapshot of the 40.0 dev channel. If you are looking to run new SIMD or pthreads tests in the shell, use this Nightly SpiderMonkey release.
  - Fixes the issue with the previous release where Emscripten SDK would require manually installing Visual Studio 2013 runtime in order to work.
   - A new command line option --build=<type> can be passed to install, activate, and emsdk_env steps (all must match) when building LLVM from source (master and incoming SDKs), where <type> is one of Debug, Release, MinSizeRel or RelWithDebInfo. This allows doing e.g. debug builds of LLVM and Emscripten optimizer for VS2013 debugging.
   - emsdk install command now has an option -jX where X is a number. This controls how many cores to use when building.
   - The directory structure of the SDK when building from source has changed in two ways: first change is that usptream LLVM decided to change their CMake build structure on Windows from build/bin/Release from build/Release/bin, so you'll see that if building manually. A second change is that the Emscripten optimizer is now built into a separate sibling directory of the Emscripten repository rather than inside the repository. This is so that the repository directories are kept clean without file changes when building from source. If you are simply using the 'emsdk activate' command, then this will not affect you. Also the path structures for precompiled tools have not changed.

Updating existing installations can be achieved via the usual steps:

cd /path/to/emsdk
./emsdk update
./emsdk install latest
./emsdk activate latest

Direct download links are at


Best,
   Jukka

Reply all
Reply to author
Forward
0 new messages