The Emscripten SDK provides the whole Emscripten toolchain (Clang, Python, Node.js and Visual Studio integration) in a single easy-to-install package, with integrated support for updating to newer SDKs as they are released.
Download one of the SDK installers below to get started with Emscripten development. The Windows NSIS installers are the easiest to set up, while the portable SDKs can be moved between computers and do not require administration privileges.
Check the relevant section below for instructions on installing your selected package.
The NSIS installers register the Emscripten SDK as a standard Windows application. To install the SDK, download an NSIS .exe file, double-click on it, and run through the installer to perform the installation.
After the installer finishes, the full Emscripten toolchain will be available in the directory that was chosen during the installation, and no other steps are necessary. If your system has Visual Studio 2010 installed, the vs-tool MSBuild plugin will be automatically installed as well.
The Portable Emscripten SDK is a no-installer version of the SDK package. It is identical to the NSIS installer, except that it does not interact with the Windows registry. This allows Emscripten to be used on a computer without administrative privileges, and means that the installation can be migrated from one location (directory or computer) to another by simply copying the directory contents to the new location.
First check the Platform-specific notes below and install any prerequisites.
Install or update the SDK using the following steps:
Download and unzip the portable SDK package to a directory of your choice. This directory will contain the Emscripten SDK.
# Fetch the latest registry of available tools. ./emsdk update # Download and install the latest SDK tools. ./emsdk install latest # Make the "latest" SDK "active" ./emsdk activate latest
On Windows, invoke the tool with
Linux and Mac OS X only: Call
source ./emsdk_env.sh after
activate to set the system path to the active version of Emscripten:
# Set the current Emscripten path on Linux/Mac OS X source ./emsdk_env.sh
This step is not required on Windows because calling the
activatecommand also sets the correct system path (this is not possible on Linux due to security restrictions).
Whenever you change the location of the Portable SDK (e.g. take it to another computer), re-run the
./emsdk activate latest command (and
source ./emsdk_env.sh for Linux).
Install the XCode Command Line Tools. These are a precondition for git.
- Install XCode from the Mac OS X App Store.
- In XCode | Preferences | Downloads, install Command Line Tools.
Install cmake if you do not have it yet:
- Download and install latest CMake from Kitware CMake downloads.
Install node.js from http://nodejs.org/
Pre-built binaries of tools are not available on Linux. Installing a tool will automatically clone and build that tool from the sources inside the emsdk directory.
Emsdk does not install any tools to the system, or otherwise interact with Linux package managers. All file changes are done inside the emsdk/ directory.
The system must have a working Compiler toolchain (because emsdk builds software from the source):
#Update the package lists sudo apt-get update # Install *gcc* (and related dependencies) sudo apt-get install build-essential # Install cmake sudo apt-get install cmake
Python, node.js or Java are not provided by emsdk. The user is expected to install these beforehand with the system package manager:
# Install Python sudo apt-get install python2.7 # Install node.js sudo apt-get install nodejs # Install Java (optional, only needed for Closure Compiler minification) sudo apt-get install default-jre
Your system may provide Node.js as
node instead of
nodejs. In that case, you may need to also update the
NODE_JS attribute of your
Git is not installed automatically. Git is only needed if you want to use tools from one of the development branches emscripten-incoming or emscripten-master:
# Install git sudo apt-get install git-core
More detailed instructions on the toolchain are provided in: Manually Building Emscripten on Linux.
The easiest way to verify the installation is to compile some code using Emscripten.
You can jump ahead to the Emscripten Tutorial, but if you have any problems building you should run through the basic tests and troubleshooting instructions in Verifying the Emscripten Development Environment.
You only need to install the SDK once! After that you can update to the latest SDK at any time using Emscripten SDK (emsdk).
Type the following (omitting comments) on the Emscripten Command Prompt:
# Fetch the latest registry of available tools. ./emsdk update # Download and install the latest SDK tools. ./emsdk install latest # Set up the compiler configuration to point to the "latest" SDK. ./emsdk activate latest # Linux/Mac OS X only: Set the current Emscripten path source ./emsdk_env.sh
The package manager can do many other maintenance tasks ranging from fetching specific old versions of the SDK through to using the versions of the tools on Github (or even your own fork). Check out all the possibilities in the “How to” guides.
If you installed the SDK using an NSIS installer on Windows, launch: Control Panel -> Uninstall a program -> Emscripten SDK.
If you want to remove a Portable SDK, just delete the directory containing the Portable SDK.
It is also possible to remove specific SDKs using emsdk.
You can always install old SDK and compiler toolchains using a current SDK. See How do I install and activate old Emscripten SDKs and tools? for more information.
On Windows, you can also install one of the old versions via an offline NSIS installer:
A snapshot of all tagged Emscripten compiler releases (not full SDKs) can be found at emscripten/releases.