| commit | 61d5ed68786c2f00cf3748179e3c066d4f6ce104 | [log] [tgz] |
|---|---|---|
| author | Sam Clegg <sbc@chromium.org> | Mon Jul 31 18:21:24 2023 |
| committer | Sam Clegg <sbc@chromium.org> | Mon Jul 31 22:34:42 2023 |
| tree | b3dfbc10a984ab24cbe24139932af069408da5f3 | |
| parent | 995ba815a9ac62b1de2d45b5bbb4b796f051cddb [diff] |
Allow certain command line settings to be additive For certain command line settings (specifically most settings that take a list) it is useful to be able to add to the existing setting rather than replace it. For example, the `-sEXPORTED_FUNCTIONS` argument. In a build system where different components can inject link flags it makes sense that each component be able add to the list of exported functions without clobbering the current list. We have had this feature requested several times in the past. For example, from the bazel toolchain folks.
Main project page: https://emscripten.org
GitHub CI status: 
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.