Standard C++ toolset
summary
Claim: C++ lacks a single standard toolset but converges on practical defaults. Survey-backed specifics: GCC still leads in many areas, one quarter of projects embed third‑party sources, and 75% of developers treat testing as integral with 67% using unit tests. Working tooling: clang-tidy/clang-format drive analysis and style, CMake presets and a new CMake debugger make builds reproducible, Conan and vcpkg gain traction, and module support lands experimentally in recent CMake/Clang/MSVC releases. Compatibility and config breakage remain the main failures.
AI-written summary · about
chapters (33)
- 0:00Intro
- 1:22What is the tool set
- 3:48Other languages
- 6:16Ruby
- 8:20Swift
- 11:57Why standard toolset matters
- 13:56Syntax style
- 16:39Standard toolset
- 17:29Package management
- 18:20C toolset
- 19:35tools creation
- 20:59compilers
- 25:57compiler options
- 26:37C20 adoption
- 27:30Clang ecosystem
- 29:23Build systems
- 30:16Developer ecosystem results
- 31:12CMake adoption
- 35:14C is a language
- 37:02Cmake and Modulus
- 38:59Compiler Flux
- 42:03Embedded dependency managers
- 45:34Code analysis
- 46:36Clank tidy
- 47:36Dataflow analysis
- 49:26C code analysis
- 50:25C code analysis tools
- 52:12Statistics
- 52:49Frameworks
- 55:46Code Coverage
- 56:10Branch Coverage
- 57:04Summary
- 57:51Outro
related talks
55mStandard C++ Toolset
52m“Tools from the C++ eco-system to save a leg”
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future
01h 01mTools from the C++ Ecosystem to save a leg
01h 28mKeynote: C++ Painkillers for C++ Developers - The Evolution of C++ Tooling
01h 01mBetter Tools in Your Clang Toolbox
51mCode Analysis ++
59mHow to start a modern C++ project?