# 使用 Homebrew, dnf, Nix, pacman, scoop 安装 vcpkg 查看 vcpkg 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。 ## 安装 ```sh sudo av install brew:vcpkg ``` 其他安装命令: ### macOS - Homebrew (100%): ```sh brew install vcpkg ``` 证据: local Homebrew formula metadata ### Linux - dnf (92%): ```sh sudo dnf install vcpkg ``` 证据: Fedora Rawhide package metadata: vcpkg from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst - Nix (92%): ```sh nix profile install nixpkgs#vcpkg ``` 证据: nixpkgs package indexes: pkgs/by-name/vc/vcpkg/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S vcpkg ``` 证据: Arch Linux sync databases: vcpkg from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ### Windows - Scoop (92%): ```sh scoop install main/vcpkg ``` 证据: Scoop official bucket manifest trees: bucket/vcpkg.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## 软件包事实 - **软件包键:** brew:vcpkg - **软件包管理器:** Homebrew - **版本:** 2026-07-27 - **来源摘要:** C++ Library Manager - **主页:** - **仓库:** - **最后更新:** 2026-08-01T02:49:51Z - **已生成:** 2026-08-03T19:37:03+00:00 ## 可执行文件 - vcpkg (别名) ## 安装行为 - Bottle: 不可用 ## 版本和新鲜度 - 页面生成时间: 2026-08-03 - 管理器版本: 2026-07-27 ## 项目历史与用法 vcpkg is Microsoft's open-source C and C++ package manager, built around a curated ports registry, a command-line tool, and integration points for native build systems. It began as a way to make Windows C++ library consumption less painful, then grew into a cross-platform workflow for Windows, macOS, Linux, and multiple target triplets. The project matters because it brought package-manager ergonomics to an ecosystem that historically depended on handwritten build instructions, vendored source trees, system packages, or project-specific CMake glue. Its package-nerd identity is the combination of source-built ports, reproducible baselines, triplets, binary caching, and manifest files checked into application repositories. ### 项目历史 The public Microsoft/vcpkg repository was created on 2016-09-15, matching Microsoft's later description of the September 2022 release as vcpkg's sixth anniversary. Early vcpkg centered on a shared installed tree and simple commands for acquiring C++ libraries; the maintained registry became the main social and technical object, with contributors adding and updating port recipes. By 2020, vcpkg's implementation was being separated into the Microsoft/vcpkg-tool repository, whose GitHub metadata describes it as the components of the vcpkg binary. That split reflects the project's maturation from a scripts-and-ports repository into a package manager with an independently released tool and a fast-moving registry. ### 采用历史 Microsoft's C++ Team reported in October 2022 that vcpkg had passed 2,000 unique open-source libraries in its public registry, with over 10,000 available port versions, 95 contributors active during that release window, 4.8k forks, and 16.8k GitHub stars. On 2026-07-02, GitHub API metadata for Microsoft/vcpkg showed more than 27k stars and 7.6k forks, indicating continued adoption in the C++ tooling community. The public vcpkg site describes a catalog of 2,849 open-source libraries, while Microsoft Learn material presents vcpkg as a free C/C++ package manager for acquiring and managing libraries and adding private libraries. The adoption story is therefore both public-registry growth and enterprise workflow growth: teams can pin baselines, use custom registries, and share binary caches in CI. ### 使用方式 Modern vcpkg use is usually manifest mode: projects commit a vcpkg.json file declaring direct dependencies and, when needed, a vcpkg-configuration.json file for registries and baselines. Microsoft Learn describes manifest mode as the recommended workflow for most users, while classic mode remains available for installing packages directly into a vcpkg tree. Package users care about triplets because vcpkg packages are built for a target configuration rather than merely downloaded as opaque archives. CI-heavy users care about binary caching, which Microsoft documents as a way to persist vcpkg-built binaries across clean build agents, including GitHub Actions workflows. ### 为什么软件包爱好者会关心 vcpkg is significant because it treats C++ package management as a build-recipe and ABI problem instead of only a download problem. Ports can encode source retrieval and build steps, triplets encode target choices, manifests encode project dependencies, and baselines make dependency versions reviewable in source control. For package maintainers, vcpkg also became a visible catalog of C and C++ library portability work. A working port is not just a version number; it is evidence that a library can be fetched, patched if necessary, configured, built, and tested across at least one supported target. ### 时间线 - 2016-09-15: The Microsoft/vcpkg GitHub repository was created. - 2020-12-08: The Microsoft/vcpkg-tool repository was created for the vcpkg binary components. - 2022-10-06: Microsoft marked vcpkg's sixth anniversary and reported more than 2,000 unique libraries in the public registry. - 2024: Microsoft Learn continued positioning manifest mode as the recommended workflow for most users. - 2026-07-02: GitHub API metadata showed Microsoft/vcpkg with more than 27k stars and active pushes on the same day. ### Related projects - vcpkg is commonly compared with Conan, system package managers, language-specific package managers, and project-local vendoring. Its closest internal companion is vcpkg-tool, the repository for the compiled tool that works with the main ports registry. - In CMake projects, vcpkg is often used through its toolchain integration, so its practical ecosystem overlaps heavily with CMake, MSBuild, Visual Studio, GitHub Actions, NuGet-style binary caches, and private source registries. ### 来源 - - - - - - - - - ## 安全说明 library-like package without higher-risk signals. - **Geiger 风险:** 绿色 / 低 - library-like 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: vcpkg.json, vcpkg-configuration.json ## 其他软件包管理器记录 - Nix - vcpkg: normalized package name match | nixpkgs package indexes: pkgs/by-name/vc/vcpkg/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - dnf - vcpkg - 2026.04.08-3.fc45: normalized package name match | Fedora Rawhide package metadata: vcpkg from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | C++ Library Manager | https://github.com/microsoft/vcpkg-tool - pacman - vcpkg - 2026.07.27-1: normalized package name match | Arch Linux sync databases: vcpkg from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | C++ library manager | https://vcpkg.io - Scoop - main/vcpkg: normalized package name match | Scoop official bucket manifest trees: bucket/vcpkg.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/vcpkg.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vcpkg.yml) ## 来源 - 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