# emscripten mit Homebrew, chocolatey, apt, MacPorts, Nix, pacman, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für emscripten in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:emscripten
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install emscripten
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install emscripten
```

  Evidenz: MacPorts ports tree: lang/emscripten/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Debian apt (92%):

```sh
sudo apt install emscripten
```

  Evidenz: Debian stable package indexes: emscripten from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

- Nix (92%):

```sh
nix profile install nixpkgs#emscripten
```

  Evidenz: nixpkgs package indexes: emscripten from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix

- pacman (92%):

```sh
sudo pacman -S emscripten
```

  Evidenz: Arch Linux sync databases: emscripten from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

### Windows

- Chocolatey (92%):

```sh
choco install emscripten
```

  Evidenz: Chocolatey community package catalog: emscripten from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','edrawings-viewer'

- Scoop (92%):

```sh
scoop install main/emscripten
```

  Evidenz: Scoop official bucket manifest trees: bucket/emscripten.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:emscripten
- **Paketmanager:** Homebrew
- **Version:** 6.0.5
- **Quellzusammenfassung:** LLVM bytecode to JavaScript compiler
- **Homepage:** <https://emscripten.org/>
- **Repository:** <https://github.com/emscripten-core/emscripten>
- **Zuletzt aktualisiert:** 2026-08-02T12:51:36+01:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- bootstrap.py (Alias)
- em++ (Alias)
- em-config (Alias)
- emar (Alias)
- embuilder (Alias)
- emcc (Alias)
- emcmake (Alias)
- emconfigure (Alias)
- emdwp (Alias)
- emmake (Alias)
- emnm (Alias)
- empath-split (Alias)
- emprofile (Alias)
- emranlib (Alias)
- emrun (Alias)
- emscan-deps (Alias)
- emscons (Alias)
- emsize (Alias)
- emstrip (Alias)
- emsymbolizer (Alias)
- wasm32-clang (Alias)
- wasm32-clang++ (Alias)
- wasm32-wasi-clang (Alias)
- wasm32-wasi-clang++ (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 6.0.5
## Projektgeschichte und Nutzung

Emscripten is the long-running LLVM-based toolchain that made C and C++ code practical to ship into JavaScript and then WebAssembly environments. Its README describes it as compiling C and C++ to WebAssembly using LLVM and Binaryen, with output that runs on the web, in Node.js, and in standalone wasm runtimes.

For package users, Emscripten is not just one compiler binary: it is a full porting toolchain with `emcc`, `em++`, build-system wrappers, archive tools, runtime helpers, ports, and a cache. Installing it from a package manager gives developers a local system toolchain, while the project itself still recommends the Emscripten SDK as the easiest way to get started.

### Projektgeschichte

The public GitHub repository dates to 2011, and the project grew around the idea that LLVM IR could be lowered into browser-executable output. As WebAssembly became the standard target, Emscripten's documented model shifted toward producing a wasm module plus JavaScript loader code, while still retaining browser, Node.js, and runtime integration layers.

The Emscripten README ties the project closely to LLVM, Binaryen, Clang, OpenGL, SDL2, and the broader portable-native-code ecosystem. Its license notes also reflect the project's LLVM relationship, including the later switch to the LLVM wasm backend.

### Adoptionsgeschichte

Emscripten became important because it turned existing native codebases into web-deployable artifacts rather than forcing rewrites. The project documentation points to large graphical and application ports, including Unity WebGL and Google Earth, as examples of the kind of portable API support it targets.

Its command-line shape made it familiar to Unix package users: `emcc` is presented as something to run like `gcc` or `clang`, and companion tools such as `emcmake` and `emconfigure` let existing C/C++ build systems cross-compile with limited ceremony.

### Wie es verwendet wird

Typical use starts with compiling a C or C++ file through `emcc`, producing JavaScript plus a WebAssembly module, or generating an HTML harness for browser testing. Larger projects commonly enter through build wrappers such as `emcmake`, `emconfigure`, and `emmake`.

The toolchain matters beyond browsers because Emscripten documents output for Node.js, Deno, Bun, and wasm runtimes. That makes it a package-manager fixture for developers who need reproducible local builds of wasm artifacts from native code.

### Warum Paket-Nerds sich dafür interessieren

Emscripten is one of the canonical examples of a package that is both a compiler and a small ecosystem: it brings a sysroot, ports, compiler frontends, JS glue generation, cache behavior, and version-sensitive ABI expectations. Its changelog explicitly warns that ABI compatibility is not guaranteed across versions and that rebuilds may be needed after upgrades.

For maintainers, Emscripten is interesting because it sits at the crossing of LLVM release behavior, browser platform changes, WebAssembly proposals, and ordinary package-manager expectations. Keeping it packaged means tracking a fast-moving compiler stack while preserving the simple user promise of `emcc hello.c -o hello.js`.

### Zeitleiste

- 2011: Public GitHub repository created for Emscripten.
- 2010s: Emscripten became a common route for porting native C/C++ applications and libraries to the web.
- WebAssembly era: The documented default model centers on producing wasm modules with JavaScript loader code.
- 2026: The 6.x release series continued active development, including toolchain, browser-target, Node.js, and wasm feature changes.

### Related projects

- LLVM and Clang provide the compiler foundation used by Emscripten.
- Binaryen is part of the documented WebAssembly toolchain used by Emscripten.
- SDL2, OpenGL support, Unity WebGL, and Google Earth are cited by the project as examples or beneficiaries of the porting model.
- Rust can integrate with Emscripten through the `wasm32-unknown-emscripten` target.

### Quellen

- <https://github.com/emscripten-core/emscripten>
- <https://raw.githubusercontent.com/emscripten-core/emscripten/main/README.md>
- <https://emscripten.org/docs/compiling/WebAssembly.html>
- <https://raw.githubusercontent.com/emscripten-core/emscripten/main/ChangeLog.md>
- <https://api.github.com/repos/emscripten-core/emscripten>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .emscripten, ~/.emscripten, $EM_CONFIG
## Andere Paketmanager-Einträge

- Debian apt - emscripten - 3.1.69+dfsg-3: normalized package name match | Debian stable package indexes: emscripten from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | LLVM-to-JavaScript Compiler | http://emscripten.org/
- Debian apt - emscripten-doc - 3.1.69+dfsg-3: normalized package name match | Debian stable package indexes: emscripten-doc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | LLVM-to-JavaScript Compiler (documentation) | http://emscripten.org/
- Nix - emscripten: normalized package name match | nixpkgs package indexes: emscripten from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix
- Ubuntu apt - emscripten - 3.1.6~dfsg-7: normalized package name match | Ubuntu 24.04 LTS package indexes: emscripten from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | LLVM-to-JavaScript Compiler | http://emscripten.org/
- Ubuntu apt - emscripten-doc - 3.1.6~dfsg-7: normalized package name match | Ubuntu 24.04 LTS package indexes: emscripten-doc from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | LLVM-to-JavaScript Compiler | http://emscripten.org/
- pacman - emscripten - 6.0.5-1: normalized package name match | Arch Linux sync databases: emscripten from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Compile C and C++ into highly-optimizable JavaScript for the web | https://emscripten.org
- MacPorts - emscripten: normalized package name match | MacPorts ports tree: lang/emscripten/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - emscripten: normalized package name match | Chocolatey community package catalog: emscripten from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','edrawings-viewer'
- Scoop - main/emscripten: normalized package name match | Scoop official bucket manifest trees: bucket/emscripten.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- MacPorts - em: installed executable or alias match | MacPorts ports tree: editors/em/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Nix - em: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/em/em/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/emscripten.yml](https://github.com/mxcl/pkgdb/blob/main/combined/emscripten.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
