From 94e7ec4f6280a80e2e929db9aa3c00fe8e066684 Mon Sep 17 00:00:00 2001 From: Ben Sima Date: Wed, 10 Apr 2024 20:31:27 -0400 Subject: Explicitly pass Bild.nix to nix builds & expose references to stable This change was motivated by my testing of tabbyAPI. I kept doing like `nix-build -A pkgs.tabbyAPI` and I thought, can't bild just do this? So I wrote a file called TabbyAPI.nix with the following contents:: { bild }: bild.pkgs.tabbyAPI and it worked, I just needed this change to Bild.hs to supply the `bild` argument. The benefit of using bild here is that I can get the logging, concurrency settings, and linking to _/nix etc all by default. Plus, using a standalone nix file like TabbyAPI.nix might be a good way to pin some package in the build system and make sure it continues to build, test, and so on. Also, thie means I don't sprinkle relative paths to the Bild.nix library throughout the repo, which is bad practice anyway. Re: explicitly exposing refernces to stable: This keeps things a bit more tidy and less confusing when working on the nix library. --- Biz/Dev/Beryllium.nix | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Biz/Dev/Beryllium.nix') diff --git a/Biz/Dev/Beryllium.nix b/Biz/Dev/Beryllium.nix index b46126d..607e5c1 100644 --- a/Biz/Dev/Beryllium.nix +++ b/Biz/Dev/Beryllium.nix @@ -1,4 +1,4 @@ -{ bild ? import ../Bild.nix { } }: +{ bild }: bild.os { imports = [ ../OsBase.nix -- cgit v1.2.3