From 6abda3aa58cdaf36b8f59740b0399c1f1a3c417d Mon Sep 17 00:00:00 2001 From: Test User Date: Fri, 24 Jul 2026 02:33:15 +0200 Subject: [PATCH] devenv: drop ninja so cmake's opusic-sys generator is deterministic Adding ninja alongside cmake let the cmake crate auto-select the Ninja generator whenever ninja happened to be on PATH. A build dir first cached under Make (ninja absent) then rebuilt with ninja present fails with "Does not match the generator used previously: Unix Makefiles". gnumake is already provided by stdenv, so keeping only cmake pins the generator to Make everywhere. Co-Authored-By: Claude Opus 4.8 (1M context) --- devenv.nix | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/devenv.nix b/devenv.nix index 3afdbc5..bc2e2d5 100644 --- a/devenv.nix +++ b/devenv.nix @@ -15,10 +15,13 @@ let pkg-config protobuf cargo-cross - # opusic-sys (via symphonia-adapter-libopus) compiles libopus from - # source with CMake; ninja is picked up automatically if present. + # opusic-sys (via symphonia-adapter-libopus) compiles libopus from source + # with CMake, using the gnumake generator from stdenv. Do NOT add ninja: + # its mere presence flips cmake's generator (Make -> Ninja), which then + # conflicts with any build dir already cached under the other generator + # ("Does not match the generator used previously"). Keeping only cmake + # makes the generator deterministic. cmake - ninja # Stream-URL sidecar for the ytdy provider: YouTube caps tokenless # stream URLs at ~1 MiB and yt-dlp is the only maintained cipher # solver (architecture/youtube-rustypipe.md, D2-revised).