Mastodawn

Tired of waiting for clean builds? Xcode 26's Compilation Cache stores build artifacts intentionally - unlike DerivedData, which is treated as disposable. The biggest wins come from branch switching, clean builds reusing cached modules, and high-churn CI environments.

🔗: https://livsycode.com/best-practices/xcode-26-compilation-cache/ by Artem Mirzabekian

#Xcode #iOSDev #BuildTimes

Xcode 26 Compilation Cache → Livsy Code

Greetings, traveler! Most iOS engineers don’t need another reminder that builds are expensive — we feel it every day. You change a few lines. You wait. You switch branches. You wait again. CI rebuilds the same targets for the tenth time today. Someone suggests cleaning DerivedData. The build gets slower, then faster, then weird again.

Livsy Code → Learn Swift the smart way

Show thread

adingbatponder

👾Nov 25, 2025

Problem was flakeRoot = "${inputs.self}" in #rust #derivation in flake caused the rust code to swallow whole flake anew for any flake file change, even changes completely unrelated to the rust code, meaning a whole rebuild. Changed that to a find_flake_dir() function that discovers flake directory by walking up if FLAKE_DIR environment variable is not set.
Took time down from always 22 mins, to 2 mins 20 sec for a minor nix fix rebuild. Ta #Claudeai #buildtime #buildtimes #nix #nixos
#flake

adingbatponder

👾Nov 25, 2025

In a #nixos #build and #switch of a #flake, my entire #rust #derivation ( which is just a program in the flake ) gets built meaning that it takes eons: even if the change to the flake that made the build necessary was a trivial change to a thing that has no interaction with the rust derivation. What am I doing wrong? Thanks for any pointers... #flakes #buildtime #buildtimes