<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Spack on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/spack/</link>
    <description>Recent content in Spack on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/spack/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted C/C&#43;&#43; Package Management: Conan vs vcpkg vs Spack Compared</title>
      <link>https://www.pistack.xyz/posts/2026-06-18-self-hosted-c-cpp-package-management-conan-vcpkg-spack/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-18-self-hosted-c-cpp-package-management-conan-vcpkg-spack/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;C and C++ development has long suffered from fragmented dependency management. Unlike Python&amp;rsquo;s pip or Rust&amp;rsquo;s Cargo, the C/C++ ecosystem lacked a unified package manager for decades. Today, three major open-source solutions have emerged: &lt;strong&gt;Conan&lt;/strong&gt; (9,413 ⭐), &lt;strong&gt;vcpkg&lt;/strong&gt; (27,186 ⭐), and &lt;strong&gt;Spack&lt;/strong&gt; (5,075 ⭐). Each takes a fundamentally different approach to solving the dependency challenge.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
