CMake and the Future of C++
summary
CMake shows concrete C++ module support: a scan→collate→compile flow that writes dynamic dependency files, reuses the Fortran machinery, and required a Ninja patch that now lands upstream so builds respect module order and avoid unnecessary rebuilds. Recent, usable features include cmake-presets.json, target precompiled headers and unity builds, Ninja multi‑config, and FetchContent/superbuilds for large dependency graphs. ctest cpack and CDash remain the supported CI/packaging pieces and JetBrains metrics put CMake at about 53% usage.
AI-written summary · about
chapters (20)
- 0:00Start
- 3:43Visible Human Projects
- 7:15What Is Cmake
- 8:20Goal of Cmake
- 9:17Cmake
- 11:24C Test
- 23:06Why Cmac Is Is Popular
- 27:09Coding with Cmake
- 29:44The Cmake Workflow
- 35:51How Does It Work for Cmake
- 37:26Pre-Process Rule
- 39:32Single Target
- 42:05Dynamic Dependency Files
- 48:52C-Macon Dependencies
- 51:26Export the Targets
- 53:40Fetch Content
- 54:16Package Managers
- 56:17New Cmake Features
- 56:31Presets
- 57:45Unity Builds
