C++ Package Manager - C++ Dependencies Don't Have To Be Painful!
summary
Survey data shows a majority of C++ developers still manage libraries manually while 19% adoption for both vcpkg and Conan climbs year‑over‑year. vcpkg’s public registry proves the claim: a 1900+ libraries catalog where updates build and validate against many targets so a git baseline yields a consistent set. C++ package managers emphasize build from source with optional binary caches, aim for reproducible dev environments, and handle diamond/ABI issues—practical tooling and validation reduce the long tail of breakage.
AI-written summary · about
chapters (15)
- 0:00C++ package management intro
- 3:35Why managing C++ dependencies is painful
- 8:06Diamond dependency problem
- 10:12VC Package solves deps
- 13:01Keep deps updated
- 14:46Key package manager features
- 21:17When to use package manager
- 25:06System package managers
- 29:39C++ package managers
- 33:09NuGet not ideal for C++
- 36:22Reproducible development environments
- 39:30Dependency management principles
- 45:48Making package managers accessible
- 50:28Live VC Package demo
- 53:17Q&A
related talks
01h 11mThe State of Package Management in C++
10mStay calm and stress-free by using a package manager: an overview of vcpkg
01h 01m10 Problems Large Companies Have Managing C++ Dependencies and How to Solve Them
28mConan, a C and C++ package manager for developers
01h 29mLibraries: A First Step Toward Standard C++ Dependency Management
57mKeynote: How To Address 7 Major C++ Pain Points with Tools
58mHow Can Package Managers Handle ABI (In)compatibility in C++?
01h 00mCommon Package Specification (CPS) in Practice: Working Implementation in Conan C++ Package Manager