kripken/emscripten — pull request #374 by SiggyBar (2012-04-11 19:27:14+00:00)
Title: Make it easier to use emscripten from a build system.

- Allow the configuration to be specified directly in the EM_CONFIG
environment variable instead of in a config file. The config file
approach has some shortcomings when using emscripten from a build
system (e.g. it uses a single global config file so it is hard to
configure emscripten in different ways from different build trees).
The presence of newlines in the EM_CONFIG string variable is used
to decide if the configuration is stored directly in the environment
variable or it is used to specify the config file.

- Skip check_sanity() and check_engine() based on the presence of
the config file. When running from a build system, it is the build
system's responsibility that everything is set up correctly. Maybe
a new environment variable EM_SKIP_CHECKS or something like that
might be better to decide whether or not to run these checks?

- Do not assume that the SPIDERMONKEY_ENGINE environment variable
is set.

- Add EM_CACHE environment variable that can be used to control
where emscripten should store built libraries.