| commit | f8efebb88a6462b997bacc8d396840a4e8975b06 | [log] [tgz] |
|---|---|---|
| author | Sam Clegg <sbc@chromium.org> | Thu Oct 29 21:28:32 2020 |
| committer | Sam Clegg <sbc@chromium.org> | Fri Oct 30 22:58:31 2020 |
| tree | 9c7d90af95a99302f5fc2eeeccbb31f987716a96 | |
| parent | 134f9959d6616b9fe53e0e52b89ef57f6b79e9b7 [diff] |
Split out post-link code in emcc and make it independently runnable This change introduces a new output format (--oformat) called `bare`. In `bare` mode emscripten will stop after running wasm-ld and output just the bare wasm module. It also introduces a new command line argument `--post-link` which take as input a raw wasm module and run all the post link phases on it (e.g. wasm-emscripten-finalize, jsifier, etc). The precise command line UI for this feature is still in the design phase so I've added a warning so that any users of this command line UI know that it is experiment.
Main project page: http://emscripten.org
Chromium builder status: emscripten-releases
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).
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.