<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>zephyr on Paul Piper</title><link>https://www.paul-piper.de/tags/zephyr/</link><description>Recent content in zephyr on Paul Piper</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>©Paul Piper</copyright><lastBuildDate>Mon, 16 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.paul-piper.de/tags/zephyr/index.xml" rel="self" type="application/rss+xml"/><item><title>Four Build Systems, One Run Button</title><link>https://www.paul-piper.de/posts/esp32-embedded-toolchains-idf-platformio-zephyr/</link><pubDate>Mon, 16 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.paul-piper.de/posts/esp32-embedded-toolchains-idf-platformio-zephyr/</guid><description>Supporting the ESP32 sounds like one job. It is four.
The same chip is reachable through four separate build systems, and they do not agree on where the toolchain lives, what counts as a project, or what the word &amp;ldquo;build&amp;rdquo; even means. I found this out the hard way while building the run configuration for Flexible for Arduino, and the plugin&amp;rsquo;s single Run button hides four completely different machines underneath it.</description></item></channel></rss>