8192916e32
These checks are rather pointless since we don't run any of these tests without thread support enabled. There are also several downsides to including this check everywhere: 1. Could lead to false positives since the fallback is simply to return zero (success). 2. Prevents the tests from being compiled and run outside of emscripten. 3. Add needless complexit to tests and needless includes of emscripten-specific headers. There are some tests that actually do look like they are designed to be run in two different modes: with real threading and with stubs. I left those tests alone, even those I can't see any cases were we actually run those tests without pthreads enabled in the test suite. |
||
|---|---|---|
| .circleci | ||
| .github | ||
| cmake/Modules | ||
| docs | ||
| media | ||
| site | ||
| src | ||
| system | ||
| tests | ||
| third_party | ||
| tools | ||
| .clang-format | ||
| .coveragerc | ||
| .editorconfig | ||
| .eslintrc.yml | ||
| .flake8 | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .style.yapf | ||
| AUTHORS | ||
| CONTRIBUTING.md | ||
| ChangeLog.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| em++ | ||
| em++.bat | ||
| em++.py | ||
| em-config | ||
| em-config.bat | ||
| em-config.py | ||
| em-dwp | ||
| em-dwp.bat | ||
| emar | ||
| emar.bat | ||
| emar.py | ||
| embuilder | ||
| embuilder.bat | ||
| embuilder.py | ||
| emcc | ||
| emcc.bat | ||
| emcc.py | ||
| emcmake | ||
| emcmake.bat | ||
| emcmake.py | ||
| emconfigure | ||
| emconfigure.bat | ||
| emconfigure.py | ||
| emdump | ||
| emdump.bat | ||
| emdwp | ||
| emdwp.bat | ||
| emmake | ||
| emmake.bat | ||
| emmake.py | ||
| emnm | ||
| emnm.bat | ||
| emprofile | ||
| emprofile.bat | ||
| emranlib | ||
| emranlib.bat | ||
| emranlib.py | ||
| emrun | ||
| emrun.bat | ||
| emrun.py | ||
| emscons | ||
| emscons.bat | ||
| emscons.py | ||
| emscripten-version.txt | ||
| emscripten.py | ||
| emsize | ||
| emsize.bat | ||
| emsize.py | ||
| package-lock.json | ||
| package.json | ||
| requirements-dev.txt | ||
README.md
Main project page: https://emscripten.org
GitHub CI status: 
Chromium builder status: emscripten-releases
Overview
Emscripten compiles C and C++ to WebAssembly using LLVM and Binaryen. Emscripten output can run on the Web, in Node.js, and in wasm runtimes.
Emscripten provides Web support for popular portable APIs such as OpenGL and SDL2, allowing complex graphical native applications to be ported, such as the Unity game engine and Google Earth. It can probably port your codebase, too!
While Emscripten mostly focuses on compiling C and C++ using
Clang, it can be integrated with other LLVM-using
compilers (for example, Rust has Emscripten integration, with the
wasm32-unknown-emscripten and asmjs-unknown-emscripten targets).
License
Emscripten is available under 2 licenses, the MIT license and the University of Illinois/NCSA Open Source License.
Both are permissive open source licenses, with little if any practical difference between them.
The reason for offering both is that (1) the MIT license is well-known and suitable for a compiler toolchain, while (2) LLVM's original license, the University of Illinois/NCSA Open Source License, was also offered to allow Emscripten's code to be integrated upstream into LLVM. The second reason became less important after Emscripten switched to the LLVM wasm backend, at which point there isn't any code we expect to move back and forth between the projects; also, LLVM relicensed to Apache 2.0 + exceptions meanwhile. In practice you can just consider Emscripten as MIT licensed (which allows you to do pretty much anything you want with a compiler, including commercial and non-commercial use).
See LICENSE for the full content of the licenses.