<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build System on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/build-system/</link><description>Recent content in Build System on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/build-system/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 2: Mastering Cargo: Rust&amp;#39;s Build System and Package Manager</title><link>https://ai-blog.noorshomelab.dev/rust-mastery-2026/mastering-cargo-toolchain/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/rust-mastery-2026/mastering-cargo-toolchain/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, aspiring Rustacean! In Chapter 1, you embarked on your Rust journey by installing &lt;code&gt;rustup&lt;/code&gt;, the powerful toolchain manager that ensures you always have the right Rust compiler and tools at your fingertips. Now, it&amp;rsquo;s time to meet Rust&amp;rsquo;s best friend and your primary companion for all things development: &lt;strong&gt;Cargo&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Think of Cargo as your personal project assistant. It’s not just a build system that compiles your code; it’s also Rust’s official package manager, a testing harness, and a documentation generator, all rolled into one. If you&amp;rsquo;ve used tools like &lt;code&gt;npm&lt;/code&gt; for Node.js, &lt;code&gt;pip&lt;/code&gt; for Python, or &lt;code&gt;Maven&lt;/code&gt;/&lt;code&gt;Gradle&lt;/code&gt; for Java, you&amp;rsquo;ll find Cargo&amp;rsquo;s role familiar, but with Rust&amp;rsquo;s unique flavor. It simplifies project creation, manages external libraries (called &amp;ldquo;crates&amp;rdquo; in Rust), builds your project, runs your tests, and much more. Without Cargo, developing in Rust would be significantly more complex and less standardized.&lt;/p&gt;</description></item><item><title>Chapter 10: Incremental Builds and File System Watching</title><link>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-10-incremental-builds/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-10-incremental-builds/</guid><description>&lt;h2 id="chapter-10-incremental-builds-and-file-system-watching"&gt;Chapter 10: Incremental Builds and File System Watching&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 10! So far, our Rust-based Static Site Generator (SSG) can parse content, apply templates, generate routes, and output static HTML. However, with every change to a source file, our SSG currently rebuilds the &lt;em&gt;entire&lt;/em&gt; site. While fast for small projects, this full rebuild approach quickly becomes a bottleneck for larger sites, leading to frustratingly long development cycles.&lt;/p&gt;
&lt;p&gt;In this chapter, we will tackle this performance issue head-on by implementing two crucial features: &lt;strong&gt;incremental builds&lt;/strong&gt; and &lt;strong&gt;file system watching&lt;/strong&gt;. Incremental builds allow our SSG to intelligently detect changes and only re-process the necessary files, drastically reducing build times. Coupled with a file system watcher, this will enable an incredibly smooth developer experience: save a file, and the site automatically rebuilds and refreshes in milliseconds, showing your changes instantly.&lt;/p&gt;</description></item></channel></rss>