Cross-Platform Pitfalls and How to Avoid Them
summary
Shows concrete workflows: a checked-in CMakePresets.json drives identical configure/build/test invocations on Windows and Linux and reproduces Visual Studio actions from the CLI; dependency management uses vcpkg and Conan patterns with vcpkg registries, baselines, constraints and overrides; binary caching restores seven packages from NuGet/GitHub Packages in ~153 ms and speeds CI; cross‑compile deploys an ARM64 Windows binary to a VM and debugs it remotely; GitHub Actions runs the same presets and executes nine passing tests.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:00Cross-platform tools landscape
- 14:36Dependency management in C++
- 21:51CMake presets and VS demo
- 43:05Debugging across platforms
- 47:21Remote debugging on ARM64 Windows
- 50:10CI pipeline with GitHub Actions
- 55:51Linux core dumps in Visual Studio
- 57:12Recap and closing remarks
related talks
24mC++ Cross-Platform Development with Visual Studio and WSL
01h 04mLatest & Greatest in Visual Studio 2019 for C++ developers
05mWindows Subsystem for Linux (WSL) Acquisition in Visual Studio
29mBash shell scripts for Windows & Linux development with Qt
13mNew Linux Development Features in Visual Studio
16mWindows-on-Arm ecosystem migration stories and maturity
29m(Ab)using GitHub Actions for building & testing kernels
32mReusing the BPF CI