ldc を Homebrew, apk, chocolatey, apt, dnf, MacPorts, Nix, pacman, zypper, scoop でインストール

プロジェクトリンク

• ホームページ
• リポジトリ
• 上流ドキュメント
• パッケージマネージャページ

コマンドとエイリアス

• ldc-build-plugin
• ldc-build-runtime
• ldc-profdata
• ldc-profgen
• ldc-prune-cache
• ldc2
• ldmd2
• timetrace2txt

プロジェクトの歴史

LDC emerged to give D programmers an LLVM-based alternative to the reference DMD compiler and GCC's GDC. The project README describes the compiler as using the official DMD frontend and LLVM as backend, with the ldc2 command as the main compiler driver.

The project evolved from early experimental D compiler work into a regular release train maintained by the ldc-developers organization. Its changelog shows the ongoing maintenance burden that matters for compilers: tracking D frontend/druntime/Phobos versions, LLVM versions, target ABI changes, platform support, and prebuilt binary packaging.

By the 1.x series, LDC had become a practical production compiler for D, not just a backend experiment. Its release notes repeatedly call out supported LLVM ranges, bundled LLVM versions for prebuilt packages, cross-compilation work, and platform fixes across Linux, macOS, Windows, Android, Alpine/musl, RISC-V, PowerPC, and other targets.

採用の歴史

LDC's adoption is tied to D users who want LLVM optimization, broader target support, link-time optimization, and packaging-friendly prebuilt compilers. Package-manager coverage across Homebrew, Debian, Ubuntu, Fedora-family systems, Alpine, Arch, Nix, Scoop, Chocolatey, MacPorts, and openSUSE-family systems reflects that it is one of the standard ways to install a D compiler.

The project also matters to downstream packagers because its behavior depends on matching D frontend/runtime versions to LLVM support windows. The changelog's repeated packaging notes, glibc baseline changes, installer changes, and bundled-runtime details are signals of a mature compiler package rather than a small standalone CLI.

使われ方

Users invoke ldc2 to compile D programs, use ldmd2 for DMD-compatible command-line behavior, and rely on helper tools such as ldc-build-runtime, ldc-build-plugin, ldc-profdata, ldc-profgen, and timetrace2txt for runtime building, plugin workflows, profiling, and build-time analysis.

The compiler is commonly selected when D code needs LLVM optimization, cross-compilation targets, sanitizer or profiling support, or integration with LLVM-adjacent workflows.

パッケージ好きにとっての重要性

LDC is package-nerd significant because compiler packages sit at the junction of language ecosystems and system toolchains. It has to coordinate D language releases, LLVM ABI/API changes, C toolchains, platform linkers, bundled runtime libraries, and distro-specific packaging constraints.

For Homebrew and other package managers, LDC is also a dependency-shaped package: installing it is not just about one executable, but about shipping a coherent compiler, runtime, standard library, config files, and helper tools.

タイムライン

• 2000s: LDC begins as an LLVM-based compiler path for the D language.
• 2016: The 1.0 release line establishes LDC as a stable D compiler package.
• 2023: LDC 1.33.0 documents semantic-analysis plugin support and adds ldc-build-plugin.
• 2024: LDC 1.38.0 documents LLVM 18 support and Android TLS/runtime changes.
• 2025: LDC 1.41.0 documents LLVM 20 support and Ubuntu 22.04-based Linux packages.
• 2026-03-01: LDC 1.42.0 documents LLVM 21 support and D frontend/druntime/Phobos version 2.112.1+.

Related projects

• Related projects include DMD, the reference D compiler whose frontend LDC tracks; GDC, the GCC-based D compiler; LLVM and Clang; and the D runtime and Phobos standard library.

ソース

• https://formulae.brew.sh/formula/ldc
• https://github.com/ldc-developers/ldc
• https://github.com/ldc-developers/ldc/releases
• https://raw.githubusercontent.com/ldc-developers/ldc/master/CHANGELOG.md
• https://wiki.dlang.org/LDC