Building Portable C++ Packages: The Bliss of Unification
summary
Shows how to build portable C++ packages by using CMake + CPack for unified build, install and packaging, plus CTest for test orchestration; warns ExternalProject downloads at build time and FetchContent doesn’t scale (causes multiple conflicting versions). Demonstrates consuming and producing packages with Conan cmake deps, creating conanfile.py that calls cmake.install or self.run for non-CMake builds, and generating a CMake toolchain file from Conan profiles to simplify cross-compilation and reproducible builds.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:32Adrian Ostrowski
- 1:31What gets unified by CMake?
- 3:58External Project
- 5:25FetchContent
- 8:24Config files
- 9:26Find modules
- 10:34Producing packages
- 12:27What's still missing?
- 13:41Specifying dependencies
- 17:34Packaging using Conan, cont'd
- 18:02Taming rebelous packages with Conan
- 18:24CMake toolchains
- 19:04Conan profiles
- 19:29Conan toolchains
- 20:23Join us at the launch event on April 9th!
related talks
01h 01mGit, CMake, Conan - How to ship and reuse our C++ projects
01h 11mThe State of Package Management in C++
01h 01mPackage management in C++
01h 20mContinuous Integration for Large Scale C/C++ Projects With Conan2
01h 04mDependency Management in C++
01h 26mOur Other C++ Interfaces
01h 12mC++ Package Manager - C++ Dependencies Don't Have To Be Painful!
01h 08m“Faster Delivery of Large C/C++ Projects with..."