Build Before Installing: Zephyr Dev Environment Using Codespaces
summary
Claim: a 23-line Dev container plus GitHub Codespaces launches VS Code in a browser and immediately builds Zephyr samples. Setup uses West, manifest repos, prebuilt container images and cached SDKs so builds work and binaries download; outcome is 95% in browser. The one missing 5–10% is USB flashing and debug; workaround is download+local flash with Nordic tools or run Docker/devcontainer locally with USB passthrough.
AI-written summary · about
chapters (9)
- 0:00Zephyr dev challenges
- 2:51Toolchain setup with CodeSpaces
- 9:02Dev Containers streamline builds
- 14:39Cloud builds download binaries
- 18:32Optimizing container pre-builds
- 21:02Run Dev Containers locally
- 24:13Cross-platform workflow limits
- 25:16Dev Containers future uses
- 26:40Resources and closing
related talks
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
41mHands on Molding VS code into a care free development environment to develop with Zephyr RTOS
41mZephyr & Visual Studio Code: How to Develop Zephyr Apps with a Modern, Visual IDE
37mZephyr Onboarding in 30 Seconds - Methods and Experiments During Zephyr Training
27mZephyr and You: A Developer Environment for Newcomers
46mZephyr Workbench: Open Source Zephyr Extension for VSCode
34mZephyr Tools for VSCode: Get Started with Zephyr Fast- 46mZephyr Workbench: Open Source Zephyr Extension for VSCode