Getting started with pepper.js on Windows

August 23, 2014

For some time now I’ve wanted to make my vector-based math application Osoasso work with Emscripten and pepper.js. Since Osoasso uses Google’s Native Client SDK to allow C++ code to execute in a browser, it is restricted to work in Google Chrome only. The pepper.js project gives the promise that the same code may work in most browsers. I’m especially interested in the performance tradeoff between C++ and JavaScript code in this case.

This week I decided to give pepper.js a try. I’ve not yet started to compile my code, but I ran into a few problems compiling and running the examples. I wanted to write down the solutions here so that others (and I) won’t need to solve the same problems again.

Getting dependencies##

Emscripten###

To use pepper.js, I first needed to install Emscripten. I was able to obtain the Emscripten SDK from this page. At the time of writing, version 1.22.0 is the latest version of the SDK. However, I’m using 32-bit Windows 7, so I had to scroll to bottom of the page and download version 1.12.0, the last version for 32-bit Windows.

Windows make###

The pepper.js README indicates the next step is to build the examples using the following command (among a few others):

make TOOLCHAIN=emscripten CONFIG=Debug

When I initially tried this, I saw a rather odd and surprising error. As it turns out, I had the D SDK installed, so the make command on my machine was running the D version of make, not the GNU version. After moving the D verison out of the way, I downloaded the GNU Win32 version of make here.

Spaces in a path##

When I ran the command above, I noticed the following output:

make -C ppapi
make[1]: Entering directory `C:/Users/Josh/Documents/development/pepper.js/examples/ppapi'
  CXX emscripten/debug/stub_emscripten.o
'C:\Program' is not recognized as an internal or external command, operable program or batch file.
make[1]: *** [emscripten/debug/stub_emscripten.o] Error 1
make[1]: Leaving directory `C:/Users/Josh/Documents/development/pepper.js/examples/ppapi'
make: *** [ppapi_TARGET] Error 2

This indicates that some part of the build system is not handling the space between the words “Program” and “Files” in the path to some executable. But which executable is the problem? I’m by no means an expert in Makefile debugging, but I did find that make has a -d option, which I used. After a good bit of output, I saw this information

Creating temporary batch file C:\Users\Josh\AppData\Local\Temp\make3560-1.bat
make[1]: Entering directory `C:/Users/Josh/Documents/development/pepper.js/examples/ppapi'
CreateProcess(C:\Users\Josh\AppData\Local\Temp\make3560-1.bat,C:\Users\Josh\AppData\Local\Temp\make3560-1.bat,...)
Putting child 0x012ada98 (emscripten/debug/stub_emscripten.o) PID 19563464 on the chain.
Live child 0x012ada98 (emscripten/debug/stub_emscripten.o) PID 19563464
  CXX emscripten/debug/stub_emscripten.o
'C:\Program' is not recognized as an internal or external command, operable program or batch file.
Reaping losing child 0x012ada98 PID 19563464
Cleaning up temp batch file C:\Users\Josh\AppData\Local\Temp\make3560-1.bat

So it seemed likely that the file make3560-1.bat was being executed and was causing the problem. Unfortunately, that file was deleted after the error.

Next, I used the -i option to cause make to continue after an error occurs. I was able to find a build which ran long enough so that I could view the contents of the makeXXX-1.bat file. Sure enough, the path to the Emscripten compiler was not quoted. Since Emscripten installed into the C:\Program Files\Emscripten\emscripten\1.12.0 directory on my computer and set the EMSCRIPTEN environment variable to point to that directory, this problem occurred. I modified the tools/nacl_emscripten.mk file to quote the paths to the Emscripten compilers, and the make command succeeded. This change has now been pulled into the pepper.js source, so it should be corrected.

Building in release##

After building in debug, the README indicates that the examples should be build in release as well, using this command

make TOOLCHAIN=emscripten CONFIG=Release

However, something does not work correctly in the release build for many of the examples. Starting with the hello_world example, I see this error:

undefined:1

^
SyntaxError: Unexpected token ILLEGAL
    at eval (native)
    at globalEval (C:\Program Files\Emscripten\emscripten\1.12.0\src\compiler.js:105:8)
    at load (C:\Program Files\Emscripten\emscripten\1.12.0\src\compiler.js:61:5)
    at Object.<anonymous> (C:\Program Files\Emscripten\emscripten\1.12.0\src\compiler.js:225:10)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
Traceback (most recent call last):
  File "C:\Program Files\Emscripten\emscripten\1.12.0\emscripten.py", line 1405, in <module>
    _main(environ=os.environ)
  File "C:\Program Files\Emscripten\emscripten\1.12.0\emscripten.py", line 1393, in _main
    temp_files.run_and_clean(lambda: main(
  File "C:\Program Files\Emscripten\emscripten\1.12.0\tools\tempfiles.py", line 39, in run_and_clean
    return func()
  File "C:\Program Files\Emscripten\emscripten\1.12.0\emscripten.py", line 1401, in <lambda>
    DEBUG_CACHE=DEBUG_CACHE,
  File "C:\Program Files\Emscripten\emscripten\1.12.0\emscripten.py", line 1288, in main
    jcache=jcache, temp_files=temp_files, DEBUG=DEBUG, DEBUG_CACHE=DEBUG_CACHE)
  File "C:\Program Files\Emscripten\emscripten\1.12.0\emscripten.py", line 292, in emscript
    assert len(output) == 2, 'Did not receive forwarded data in an output - process failed? We only got: ' + output[0][-3000:]
AssertionError: Did not receive forwarded data in an output - process failed? We only got:
Traceback (most recent call last):
  File "C:\Program Files\Emscripten\emscripten\1.12.0\emcc", line 1525, in <module>
    final = shared.Building.emscripten(final, append_ext=False, extra_args=extra_args)
  File "C:\Program Files\Emscripten\emscripten\1.12.0\tools\shared.py", line 1276, in emscripten
    assert os.path.exists(filename + '.o.js') and len(open(filename + '.o.js', 'r').read()) > 0, 'Emscripten failed to generate .js: ' + str(compiler_output)
AssertionError: Emscripten failed to generate .js:
make[1]: *** [emscripten/Release/hello_world_unstripped.js] Error 1
make[1]: Leaving directory `C:/Users/Josh/Documents/development/pepper.js/examples/hello_world'
make: *** [hello_world_TARGET] Error 2

I’m not sure about the cause of this problem, but it may be similar to this issue reported recently. In spite of this problem, we can still verify that the debug build of the examples worked.

Update 2014-08-26: I was able to work around the problem above by using the command line:

make TOOLCHAIN=emscripten CONFIG=release

Note that the “r” in “release” is lowercase instead of uppercase. It seems this problem is not the same as the issue I linked to above. This change does correct the problem and allow the release build of the examples to complete for me though.

Testing the debug examples##

After running the local web server to test the examples, I found that none of them were working! This occurs because the website uses the release build of the examples, which is not available. It is relatively easy to use the debug build of the example though. First, select the “Developer Mode” option near the bottom of the examples site:

Select developer mode

This will enable a “Config” section of the site, which will allow you to switch to the debug build, where the examples should work.

Use debug configuration

Conclusion##

With these few tweaks, I was able to get the pepper.js examples working well on Windows. The next step is to build my project!


Content © Josh Peterson

Site design by Sirupsen