So, you want to use C++ Modules ...cross platform
summary
Clear, practical state: MSVC is feature-complete for modules while clang and GCC are still partial; module builds need BMI compatibility, compiler-specific file extensions, and build-system dependency scanning. CMake (3.25–3.28) plus Ninja or MSBuild produce module maps and handle BMI outputs. Demo compiles a modularized app with libc++ on Linux; measured costs: umbrella header ~2s, header unit ~15ms, imported module <1 ms. Examples show real failures, required global-module fragments, and concrete migration steps.
AI-written summary · about
chapters (9)
- 0:00Cross-platform C++ modules intro
- 2:12C++ modules basics recap
- 16:56Compiler implementations status
- 23:30Modularizing libraries step-by-step
- 35:42Build systems support
- 44:47Module dependencies scanning
- 48:52Live demo modular app
- 54:05Conclusion and future
- 55:56Q&A
related talks
57mA (Short) Tour of C++ Modules
01h 38mProgramming in the Large With C++ 20
48mMultiplatform C++
01h 03mWhat I Talk About When I Talk About Cross Platform Development
30mModularization
01h 00mMicrosoft w/ C++ to Deliver Office Across Different Platforms, Part I
01h 07mModular Code with Examples in C#
01h 00mC++ Mythbusters