The State of Package Management in C++
summary
Status update on C++ packaging in 2019: two practical options dominate — Conan: 300 curated packages, binary caching and decentralised remotes focuses on private repos and reusing prebuilt binaries; vcpkg: ~800 packages in a single git repo emphasizes massive curation and source builds per machine. Both integrate with CMake (generators/toolchain files), handle Windows/Linux/macOS, and surface the diamond/version-conflict problem; advice: keep builds simple, declare dependencies and avoid hidden build-time tools.
AI-written summary · about
chapters (32)
- 0:00Intro
- 1:00Workflow
- 1:57Introduction
- 3:37Why
- 5:30Out of the box
- 6:10Hard computation
- 8:35Thirdparty libraries
- 9:23Why are we doing this
- 10:35What is package management
- 14:29Use cases
- 17:15Binary
- 19:38Free Platform
- 21:01Existing Ecosystem
- 22:04Encapsulation
- 23:07Diamond Problem
- 26:32Con
- 34:45PowerVC
- 36:15C Make
- 36:33Repository
- 37:45Packaging
- 39:23Cons
- 43:50Be Creative
- 47:29Atom
- 48:13Build dependencies
- 49:15Hiding dependencies
- 51:25SSL
- 52:16Dependencies
- 53:20ABI
- 55:06Guide
- 56:37Debugging
- 57:30Toolchain
- 58:02Whats next
related talks
01h 03mC++ Package Manager - C++ Dependencies Don't Have To Be Painful!
01h 01mPackage management in C++
01h 12mC++ Package Manager - C++ Dependencies Don't Have To Be Painful!
01h 04mDependency 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
42mManage code dependencies at work with new vcpkg features
09mAn Overview of vcpkg in 10 Minutes