There were some talks at GDC this year on Empscripten, and regrettably I missed those. And just last week Unreal Engine 3 was ported to the browser using Emscripten. Thanks to recent optimization work, and the new AsmJS spec, its seems Emscripten code is close to 2x slower than Native in AsmJS optimized browsers. And as always, a great place to hear about interesting new things with Emscripten is on the lead developers blog and twitter.
Now formalities are out of the way, I’ve given myself a new project: Squirrel VM in the browser.
This blog post wont cover “SquirrelyJS” (a nickname I just came up with for the project), but setting up Emscripten again.
Setting Up Emscripten
I’ve just recently installed a new hard drive in my laptop, so I need to reinstall Emscripten. I’ll be following the tutorial here:
It’s worth knowing that the Emiscripten you get out of GIT is the full thing usable as-is. No compiling is required. Once everything is installed correctly (Clang, Python), and your paths are set up correctly, it will work.
Python 2.7 I already had installed in C:\Python27. Emscrpten tries to be clever and use a file python2.exe, which doesn’t exist by default. This can be fixed later, but you can create a symlink, or make a copy of python.exe as python2.exe in the python directory. It’s 27k, so an extra copy of python.exe wont hurt.
I use MinGW with MSys, and while yes there is an “experimental” download on the Clang/LLVM page, I wasn’t able to get it working. So instead, I had to build it from source.
WARNING: DO NOT BUILD FROM SVN! EMSCRIPTEN IS ONLY COMPATIBLE WITH THE CURRENT STABLE RELEASE! (Also skip the test-suite)
I followed the instructions here, with one change:
EDIT: USE AS REFERENCE ONLY! You should only ever use the stable sources. Uncompress clang in to the tools folder as suggested (renaming clang-3.2.src to just clang), and optionally in projects compiler-rt (renaming compiler-rt-3.2.src to just compiler-rt). Skip the test-suite.
My change I did “../llvm/configure --enable-optimized --disable-assertions“, since I wanted a nice fast release build of LLVM+Clang, not a slower debug build with Asserts.
I also had to disable my current install of Clang, as it was trying to use Clang to build Clang+LLVM, which was broken. Only a problem if you tried to use the experimental package they provided.
An unfortunate downside, I was unable to use “make -j 4“, which uses multiple cores to compile. This is the 2nd time in the years I’ve been using MinGW+Msys I’ve come across something that make’s -j hasn’t worked (I can’t remember what the other one was, but it was a few weeks ago). It deadlocked on compiling the 4th file, which is not a good way to finish building anything. 😉
Compiling in a single thread took me over an hour. 🙁
Once built, “make install” to put it in my /usr/local/bin.
Configuring your system for Emscripten
First things first, we’re going to need to set some environment variables. You can do that here:
Control Panel->System->Advanced System Settings->Environment Variables
The Path is often the most important variable to tweak. Add new paths separated by semicolons (;). I added:
There are some optional environment variables you can add here too.
EMSCRIPTEN – Where emscripten is (e.g. “C:\Emscripten\”).
LLVM – Where Clang+LLVM is. (e.g. “c:\MinGW\\msys\\1.0\\local\\bin”).
PYTHON – Python executable. (i.e. “C:\Python27\python.exe”).
Browse to the Emscripten directory with MSys, and run the following.
Because its the first run, this will create an Emscripten configuration file in your home folder. Mine was here:
In this file you can edit/set the location of Python, Clang/LLVM, etc. You can also change it from using python2.exe to python.exe if you want.
IMPORTANT: You need to set your temp directory. I modified the TEMP_DIR line as follows:
TEMP_DIR = os.path.expanduser(os.getenv('TMP') or '/tmp')
After all, the rest of the lines in the file use this os.getenv function, so why not temp too?
Okay! That should be it.
Now if everything is set up correctly, you should be able to run clang and have it not crash.
You should also be able to run emcc without explicitly invoking python now.
Node is NodeJS, the tool for running JS files on the command line (without an .html page).