2.0.5
2 files changed
tree: 01ddbcdc45cb5d3ae6c69c9e09d66526cd18be4c
  1. .circleci/
  2. .github/
  3. cmake/
  4. docs/
  5. media/
  6. site/
  7. src/
  8. system/
  9. tests/
  10. third_party/
  11. tools/
  12. .clang-format
  13. .editorconfig
  14. .flake8
  15. .gitattributes
  16. .gitignore
  17. .style.yapf
  18. AUTHORS
  19. ChangeLog.md
  20. CONTRIBUTING.md
  21. em++
  22. em++.bat
  23. em++.py
  24. em-config
  25. em-config.bat
  26. em-config.py
  27. emar
  28. emar.bat
  29. emar.py
  30. embuilder
  31. embuilder.bat
  32. embuilder.py
  33. emcc
  34. emcc.bat
  35. emcc.py
  36. emcmake
  37. emcmake.bat
  38. emcmake.py
  39. emconfigure
  40. emconfigure.bat
  41. emconfigure.py
  42. emmake
  43. emmake.bat
  44. emmake.py
  45. emranlib
  46. emranlib.bat
  47. emranlib.py
  48. emrun
  49. emrun.bat
  50. emrun.py
  51. emscons
  52. emscons.bat
  53. emscons.py
  54. emscripten-version.txt
  55. emscripten.py
  56. emsize
  57. emsize.bat
  58. emsize.py
  59. LICENSE
  60. Makefile
  61. package-lock.json
  62. package.json
  63. README.md
  64. requirements-dev.txt
README.md

emscripten logo

Main project page: http://emscripten.org

GitHub CI status: CircleCI

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.