Getting Rid of "It Works on my Machine"
summary
Chooses Docker to pin exact tool versions per project, building a single image that includes ESP-IDF 4.4.1, GCC and third‑party installers (STM32 Cube, GCC 15), plus VS Code and CLI integration so builds and codegen run identically in CI and locally. Debugging and GUI tools work via USB passthrough on all platforms except newest Mac M1s (USB passthrough supported except M1). Uses multi‑FROM composition to merge microcontroller toolchains into a single project Dockerfile; implementation requires one maintainer but gives reproducible builds.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:32The embedded development problem
- 2:02Evaluating potential solutions
- 4:42How Docker works for development
- 6:16Building custom Docker files
- 9:17Project-wide implementation
- 11:07Q&A session
related talks
55mOvercoming C++ Embedded Development Tooling Challenges
56mCross Platform Enablement for the Yocto Project with Containers
46mSponsored Session: Building the IDE Golden Path
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
46mBuilding for Enterprise by Testing OSS: One Codebase to Rule Them All- 46mBuilding the IDE Golden Path
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
46mWrite Once, Run Anywhere? Building Perfect Docker Images for Java Apps