<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cmake on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cmake/</link>
    <description>Recent content in Cmake on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cmake/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>C&#43;&#43; Project Scaffolding and Build Configuration: CPM.cmake vs Meson vs build2 in 2026</title>
      <link>https://www.pistack.xyz/posts/2026-07-30-cpp-project-scaffolding-build-configuration-cpm-cmake-meson-build2/</link>
      <pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-30-cpp-project-scaffolding-build-configuration-cpm-cmake-meson-build2/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;C++ project setup has historically been one of the language&amp;rsquo;s biggest pain points. Unlike Rust (cargo), Go (go mod), or Node.js (npm), C++ has no standard build system or package manager. This fragmentation has spawned dozens of build tools, each with different philosophies — from CMake&amp;rsquo;s near-universal dominance to Meson&amp;rsquo;s speed-first design and build2&amp;rsquo;s integrated build-and-package approach.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
