pkg.sopackage field notes

brew / Rang 5702

build2 mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install build2

provider-native install command

Überblick

Paketzusammenfassung

C/C++ Build Toolchain

Befehle und Aliase

  • b
  • bdep
  • bpkg
  • bx

Verlauf

Projektgeschichte und Nutzung

build2 is a cross-platform, MIT-licensed C/C++ build toolchain made of a build system, package manager, project manager, and supporting libraries.

Projektgeschichte

The build2 project started in the mid-2010s with documentation copyright dating from 2014 and public toolchain tags beginning at 0.1.0. Its stated goal is to approximate Rust Cargo's convenience for C and C++ while keeping enough depth for complex real-world build requirements.

The toolchain is intentionally hierarchical: `b` is the general-purpose build system, `bpkg` handles package consumption, and `bdep` handles project development. The `build2-toolchain` repository is an amalgamation used to build and package those components together.

Adoptionsgeschichte

build2 has remained a specialist C/C++ toolchain rather than a default ecosystem standard like CMake, but its own community page says it is used for real development and cites customer-facing software such as ODB and XSD. The project also maintains cppget.org as its package repository.

It is packaged by Homebrew, Nix, Fedora-style `bdep` packages, and Windows winget according to the input. Upstream development happens in self-hosted git repositories on git.build2.org with GitHub mirrors for collaboration.

Wie es verwendet wird

Users typically create or initialize projects with `bdep`, build with `b`, and consume dependencies with `bpkg`. The documented configuration surface includes project-local `build/config.build`, `.build2/` state, `.build2/local/`, user-level `~/.build2/`, and system-level `/etc/build2/` locations.

The toolchain is aimed primarily at C/C++ and mixed-language projects involving C or C++, though the project describes a longer-term universal build-toolchain goal.

Warum Paket-Nerds sich dafür interessieren

build2 is significant because it is one of the more complete attempts to give C and C++ a Cargo-like combined build, package, and project-management workflow without hiding the complexity needed by native-code builds.

For package managers, it is also recursive in an interesting way: the build2 toolchain is used for its own development, and the upstream amalgamation repository exists specifically to make source builds and binary packaging of the whole toolchain practical.

Zeitleiste

  • 2014: build2 documentation copyright begins, marking the early public project era.
  • 2010s: Public 0.x toolchain tags began with 0.1.0 and evolved through the pre-1.0 series.
  • 2018: The project pointed users to a CppCon 2018 presentation as a toolchain overview.
  • 2020s: The community page described build2 as in the final stage of pre-1.0 development and already used in projects such as ODB and XSD.
  • 2026: The Toolchain Introduction metadata showed version 0.18 and copyright through 2026.

Related projects

  • Cargo is the explicit convenience benchmark named by the build2 homepage.
  • CMake and Autotools are common neighboring C/C++ build-system incumbents, though build2 packages build, dependency, and project management together.
  • cppget.org is the build2 package repository referenced by the project community page.

Sicherheitslage

Risikostufe: yellow

generalized runtime or code generation signal.

Risikoklassifikator

yellow Risiko · mittel Konfidenz · runtime

Warum

  • generalized runtime or code generation signal

Signale

  • text:build tool

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

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

Config paths the tool may read or write during local use.

Unix
build/config.build.build2/.build2/local/~/.build2//etc/build2/

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
bExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
bdepExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
bpkgExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
bxExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version0.18.1
Manager aktualisiert2026-06-27
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:build2
Version0.18.1
PaketmanagerHomebrew
Homepagehttps://build2.org
Zuletzt aktualisiert2026-06-27T13:57:07Z
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation