| commit | fb7b9f743815f81204a8d382763fde72c7158566 | [log] [tgz] |
|---|---|---|
| author | Sam Clegg <sbc@chromium.org> | Fri Apr 16 16:51:14 2021 |
| committer | Sam Clegg <sbc@chromium.org> | Tue Apr 27 15:03:57 2021 |
| tree | 8945fa831053f7ec8d261767d533100ba7e1fa47 | |
| parent | f039cfa13a3c7e2045eb96df28785e20694af402 [diff] |
Remove the "first use generates config file" magic I think its cleaner if just exit with an error if emscripten is not yet configured. Especially since we already have an error mesasge for "config file not found" so this change means that first time users will now see that message (in which we now recommend the use of `--generate-config`). There are couple of reasons why I think this is a good idea: 1. We already have a error message for missing config file 2. Currently when the config file is generated we return 0 without actually doing anything, which could confuse build systems. 3. In the case of a misconfigured systems (e.g. an accidentailly removed config file, or a EM_CONFIG pointing the wrong place) the solution is probably not to simply just create a new config, but to inform the developer and let them take action.
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.