How to Herd 1,000 Libraries
summary
vcpkg enforces reproducible sources by preferring git commit IDs and verifying archives with sha-512 hashes, falling back to git clones for hosts that embed timestamps. Builds use isolated tool copies (Python, Ninja, CMake), many packages get rewritten to a short CMake wrapper or have the upstream build wrapped; transitive fixes come from a cmake find_package hook that injects missing deps. The result: a catalog of 1,000+ libraries (≈850 Linux, ≈800 Mac) built consistently.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:13Single library build
- 8:00Build system challenges
- 17:05Dependency handling
- 23:45Artifact packaging
- 26:37Ecosystem upgrades
- 30:35Key takeaways
related talks
09mAn Overview of vcpkg in 10 Minutes
10mStay calm and stress-free by using a package manager: an overview of vcpkg
42mManage code dependencies at work with new vcpkg features
01h 11mThe State of Package Management in C++
42mUsing vcpkg in anger
21mBuilding Portable C++ Packages: The Curse of Abundance
01h 01mPackage management in C++
01h 12mC++ Package Manager - C++ Dependencies Don't Have To Be Painful!