import CMake, CMake and C++20 Modules
summary
CMake ships an experimental C++20 modules workflow in CMake master that uses per‑target file sets and compiler scanning to emit JSON dependency files, collates those with scan dependencies, and drives Ninja’s dynamic dependencies so builds run in correct order. Visual Studio 2022 preview and a patched GCC produce the required scan output and the example builds and ninja installs succeed; clang still lacks the standardized scanner support.
AI-written summary · about
chapters (23)
- 0:00Start
- 0:14Introduction to Kitware
- 0:44Where Did the Cmake Thing Come from and How Do We Get Involved
- 4:53Minecraft
- 8:07Basic Cmake Workflow
- 9:55Modern Cmake
- 10:58Usage Requirements
- 12:19Cmake Presets
- 12:58Pre-Compiled Headers
- 15:08Testing
- 16:16Processor Affinity
- 16:48C plus Modules
- 19:40Dynamic Dependencies
- 23:50Create a File Format
- 24:02Json File Format
- 24:43Scan Dependencies
- 26:43Installing Header on Libraries before File Set
- 26:53Library Eigen Interface
- 30:58Named Modules
- 43:39New Cmake Features
- 49:38Verbose Environment Variable
- 52:03Switching Json Libraries
- 52:54Are There any Tools To Migrate Existing Build Systems to Cmake
related talks
01h 02mCMake and the Future of C++
01h 07mC++20 Modules: The Packaging and Binary Redistribution Story
01h 08mC++20 Modules, 5 Years Later
01h 01mClean CMake for C++ (library) developers
01h 05mModules are coming
01h 38mC++20: Reaching for the Aims of C++
05mC++ Modules and Packages: Making Dreams Come True
55mC++ 20 Innovations: High-Performance Cross-Platform Architecture in C++