.
4 files changed
tree: b1433431ecb6a290588049517d4f519e3b5385f7
  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. .gitmodules
  18. .style.yapf
  19. AUTHORS
  20. ChangeLog.md
  21. CONTRIBUTING.md
  22. em++
  23. em++.bat
  24. em++.py
  25. em-config
  26. em-config.bat
  27. em-config.py
  28. emar
  29. emar.bat
  30. emar.py
  31. embuilder
  32. embuilder.bat
  33. embuilder.py
  34. emcc
  35. emcc.bat
  36. emcc.py
  37. emcmake
  38. emcmake.bat
  39. emcmake.py
  40. emconfigure
  41. emconfigure.bat
  42. emconfigure.py
  43. emmake
  44. emmake.bat
  45. emmake.py
  46. emranlib
  47. emranlib.bat
  48. emranlib.py
  49. emrun
  50. emrun.bat
  51. emrun.py
  52. emscons
  53. emscons.bat
  54. emscons.py
  55. emscripten-version.txt
  56. emscripten.py
  57. emsize
  58. emsize.bat
  59. emsize.py
  60. LICENSE
  61. Makefile
  62. package-lock.json
  63. package.json
  64. README.md
  65. 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.