/en/tags/rust/Recent content in Rust on Xerxes II's BlogHugoenMon, 06 Apr 2026 00:00:00 +0000/en/posts/cross-compile-rust-freebsd-zigbuild/Mon, 06 Apr 2026 00:00:00 +0000/en/posts/cross-compile-rust-freebsd-zigbuild/<p>Notes on cross-compiling a Rust project from Linux (x86_64) to FreeBSD x86_64 using <code>cargo-zigbuild</code>, and the pitfalls I ran into along the way. The project is a Discord bot that depends on crates like <code>sysinfo</code>, <code>tikv-jemallocator</code>, and <code>sea-orm</code> (SQLite).</p> <h2 id="background">Background</h2> <p>Zig ships with a multi-platform libc and cross-compilation toolchain. <code>cargo-zigbuild</code> leverages Zig as the linker to enable Rust cross-compilation — usually much more convenient than setting up a cross toolchain yourself. That said, targeting FreeBSD comes with some unique gotchas.</p>/en/posts/optimize-rust-compile-time-space/Mon, 06 Apr 2026 00:00:00 +0000/en/posts/optimize-rust-compile-time-space/<p>Slow compilation and massive <code>target/</code> directories — the classic Rust complaints. This post documents the techniques I&rsquo;m currently using to make things better, using my project <a href="https://github.com/Xerxes-2/clewdr">ClewdR</a> (an async web service with 394 crate dependencies) as an example.</p> <p>Environment: Rust 1.94.1, CachyOS (Arch-based), NVMe SSD, Btrfs.</p> <h2 id="rust-lld">rust-lld</h2> <p>Linking is the final step of Rust compilation, and traditionally the slowest. GNU ld performs terribly here, especially with LTO enabled.</p> <p>The old approach was to manually install <code>lld</code> or <code>mold</code> and configure <code>.cargo/config.toml</code>:</p>