# Installer boost-bcp avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de boost-bcp pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:boost-bcp
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install boost-bcp
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:boost-bcp
- **Gestionnaire de paquets:** Homebrew
- **Page du gestionnaire de paquets:** <https://formulae.brew.sh/formula/boost-bcp>
- **Version:** 1.90.0
- **Résumé source:** Utility for extracting subsets of the Boost library
- **Page d'accueil:** <https://github.com/boostorg/bcp>
- **Dépôt:** <https://github.com/boostorg/bcp>
- **Docs amont:** <https://github.com/boostorg/bcp#readme>
- **Licence:** BSL-1.0
- **Archive source:** <https://github.com/boostorg/boost/releases/download/boost-1.90.0/boost-1.90.0-b2-nodocs.tar.xz>
- **Dernière mise à jour:** 2026-06-25T13:37:37+02:00
- **Généré:** 2026-07-08T07:18:31+00:00

## exécutables

- bcp (cli)
- bcp (alias)

## Dépendances de compilation

- boost-build

## Comportement d'installation

- hook post-installation: non défini
- Bouteille: disponible sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Version et fraîcheur

- page générée: 2026-07-08
- version du gestionnaire: 1.90.0
- gestionnaire mis à jour: 2026-06-25
- données locales: OK
- dépôt amont: https://github.com/boostorg/boost
- info: No cached GitHub release or tag data was available.
## Historique du projet et usages

Boost BCP is the Boost project utility for extracting a usable subset of Boost and its dependencies. It is aimed at Boost authors who distribute a library outside Boost and at application developers who want to vendor only the Boost pieces they need.

### Historique du projet

The boostorg/bcp Git history contains an initial commit adding the BCP utility in June 2003, followed quickly by dependency-analysis fixes and the report mode. That places BCP in the early era when Boost was becoming a large, modular C++ library collection and users needed tooling to manage subsets.

The official BCP documentation, copyrighted 2009 by John Maddock, describes the core job that has remained stable: copy headers, library source, build files, and transitive dependencies for a named Boost component or for dependencies discovered by scanning user code. It can also generate HTML reports listing licenses, copyright holders, and dependency reasons.

BCP continued to be released with Boost version tags after Boost moved to the modular GitHub organization. The tool's repository carries Boost release tags from the 1.31 era onward, and its README points users to the canonical boost.org documentation.

### Historique d'adoption

BCP is not a mainstream end-user command so much as a specialist tool for C++ packaging and vendoring. Its adoption follows Boost itself: wherever developers wanted a subset of Boost without shipping the full tree, BCP provided an official route.

Homebrew's separate boost-bcp formula reflects package-manager recognition that this utility is useful on its own, even when the complete Boost distribution is available separately. That split is exactly the sort of detail package maintainers care about: one executable from a giant upstream project, packaged for a narrow but real workflow.

### Modes d'utilisation

The documented examples include copying `boost/scoped_ptr.hpp` and dependencies, copying Boost.Regex with source and build files, copying whole libraries, renaming the Boost namespace for vendored builds, scanning non-Boost source files for Boost includes, and generating HTML dependency/license reports.

BCP intentionally follows broad dependency paths because a portable Boost subset must often include headers for multiple compilers, platforms, and preprocessor branches. The docs warn that dependency sets can look fat compared with what one compiler happens to use.

### Pourquoi les passionnés de paquets s'y intéressent

Boost BCP is deeply package-nerd significant because it is an upstream-sanctioned answer to vendoring before modern C++ dependency managers were common. It turns a huge source distribution into a smaller redistributable tree while preserving transitive headers, compiled-library source, build metadata, and license accounting.

It also exposes a tension every C++ package maintainer knows: header-only libraries are not really dependency-free once portability macros, compiler workarounds, and optional source libraries enter the graph. BCP's deliberately conservative dependency expansion is a historical artifact of Boost's promise to work across many compilers and platforms.

### Chronologie

- 2003-06-09: Initial Git history entry adds the BCP utility.
- 2003-06-23: Dependency-analysis fixes and report mode are added.
- 2004-02-04: boost-1.31.0 tag appears in the BCP repository history.
- 2009: Official QuickBook documentation records John Maddock copyright and BCP usage model.
- 2010s: Boost's modular GitHub organization makes BCP available as boostorg/bcp while still releasing with Boost.
- 2024: Recent Boost release tags continue to include the BCP repository.

### Related projects

- Boost is the parent C++ library collection and release ecosystem.
- Boost.Build is related because BCP can copy build files and the build system for selected libraries.
- Boost.Regex is a prominent documented example because BCP can copy its headers, source, build data, and dependencies.
- boostdep is related as another Boost tool for dependency work in the modular repository era.

### Sources

- <https://github.com/boostorg/bcp#readme>
- <https://github.com/boostorg/boost#readme>
- <https://raw.githubusercontent.com/boostorg/bcp/develop/doc/bcp.qbk>
- <https://www.boost.org/doc/libs/release/tools/bcp/doc/html/index.html>
- source_facts.package-manager


## Notes de sécurité

library-like package without higher-risk signals.

- **Risque Geiger:** vert / faible
- library-like package without higher-risk signals

## Détails de la base source

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** boost-bcp
- **Version Scheme:** 0
- **Revision:** 0
- **Head Version:** HEAD
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** head, stable


## Liens liés

- [Source-control packages](https://www.automicvault.com/fr/pkg/source-control-tools/) - Belongs to a source-control command family.
- [Terminal utility packages](https://www.automicvault.com/fr/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://www.automicvault.com/fr/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [Developer build packages](https://www.automicvault.com/fr/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata.
- [cabin](https://www.automicvault.com/fr/pkg/brew/cabin/) - Shares av.db curated category or tags: cli, cpp, developer-tools.
- [clang-include-graph](https://www.automicvault.com/fr/pkg/brew/clang-include-graph/) - Shares av.db curated category or tags: cli, cpp, developer-tools.
- [clangql](https://www.automicvault.com/fr/pkg/brew/clangql/) - Shares av.db curated category or tags: cli, cpp, developer-tools.
- [clazy](https://www.automicvault.com/fr/pkg/brew/clazy/) - Shares av.db curated category or tags: cli, cpp, developer-tools.
- [conan](https://www.automicvault.com/fr/pkg/brew/conan/) - Shares av.db curated category or tags: cli, cpp, developer-tools.
- [etl](https://www.automicvault.com/fr/pkg/brew/etl/) - Shares av.db curated category or tags: cli, cpp, developer-tools, libraries.
- [include-what-you-use](https://www.automicvault.com/fr/pkg/brew/include-what-you-use/) - Shares av.db curated category or tags: cli, cpp, developer-tools.
- [metashell](https://www.automicvault.com/fr/pkg/brew/metashell/) - Shares av.db curated category or tags: cli, cpp, developer-tools.
- [vcpkg](https://www.automicvault.com/fr/pkg/brew/vcpkg/) - Local package facts share a topical domain. Shared terms: cli, cpp, developer, developer-tools, libraries.
- [thors-anvil](https://www.automicvault.com/fr/pkg/brew/thors-anvil/) - Local package facts share a topical domain. Shared terms: boost, cli, developer, developer-tools, libraries.

## Combined YAML source

View the package source record on GitHub. [combined/boost-bcp.yml](https://github.com/automic-vault/db/blob/main/combined/boost-bcp.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- cross-ecosystem install command graph