Level Up Your Debugging Workflow with CMake Presets, Disassembly View, & GitHub Actions
summary
Demonstrates using cmakepresets.json (requires CMake 3.21+) and the CMake Tools extension to build the same C++ project across three OSes and two editors, runs a clean build and ctest (1/1 passing), and shows vcpkg auto-installing fmt and gtest; debugs a Raspberry Pi blink program with a conditional breakpoint after 10 blinks and a live change from 1000ms to 500ms; inspects generated machine code with disassembly view and adds a GitHub Actions pipeline using a self‑hosted Raspberry Pi runner; previews vcpkg artifacts.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:53Use CMake Presets to easily debug the same project on different platforms and in different editors/IDES
- 13:03Use CMake Presets to build and debug a Fibonacci program in Visual Studio, VS Code, and from the command line across Windows, Linux, and Mac
- 30:05Use Disassembly View to understand how data is represented in memory
- 32:29Debug a Blink program on a Raspberry Pi using CMake Presets and Disassembly View in
- 39:06Automatically catch bugs in your program before shipping to production by setting up a CI/CD pipeline
- 43:05Use GitHub Codespaces to create consistent, fast, and clean development environments accessible from your browser
- 44:32Use GitHub Actions and GitHub Codespaces to debug, build, and test our Blink program in the cloud
related talks
01h 04mNew in Visual Studio Code! Clang-Tidy, makefile, CMake, GitHub, & More
36mC++ Development with Visual Studio Code
01h 00mCollaborative C++ Development with Visual Studio Code
01h 00mCross-Platform Pitfalls and How to Avoid Them
01h 01mDebugging Assembly Language and GPU Kernels in Visual Studio Code
59mHow to start a modern C++ project?
52mNew in Visual Studio: CMake Debugger, Better Diagnostics, and Video Games
50mGitHub Features Every C++ Developer Should Know