Flake Utils - Revision history

Mightyiam: Link to Nixcademy blog post on (not using) flake-utils

2025-12-26T06:35:03Z

Link to Nixcademy blog post on (not using) flake-utils

← Older revision		Revision as of 06:35, 26 December 2025
Line 53:		Line 53:
	}		}
	</syntaxhighlight>		</syntaxhighlight>

			== See also ==

			* [https://nixcademy.com/posts/1000-instances-of-flake-utils/ 1000 Instances of flake-utils, Nixcademy]

	[[Category:Flakes]]		[[Category:Flakes]]

Malix: syntax

2025-09-14T16:41:14Z

syntax

← Older revision		Revision as of 16:41, 14 September 2025
Line 1:		Line 1:
	{{Warning\|using flake-utils is [https://ayats.org/blog/no-flake-utils not recommended]. use [[Flake Parts]] instead}}		{{Warning\|using flake-utils is [https://ayats.org/blog/no-flake-utils not recommended]; if you want to use a flake framework, use [[Flake Parts]] instead.}}

	[https://github.com/numtide/flake-utils flake-utils] is a collection of pure Nix functions that don't depend on [[Nixpkgs]], and that are useful in the context of writing other [[Flakes\|Nix Flakes]].		[https://github.com/numtide/flake-utils flake-utils] is a collection of pure Nix functions that don't depend on [[Nixpkgs]], and that are useful in the context of writing other [[Flakes\|Nix Flakes]].

Malix: add link

2025-09-14T16:38:10Z

add link

← Older revision		Revision as of 16:38, 14 September 2025
Line 1:		Line 1:
	{{Warning\|using flake-utils is not recommended. use [[Flake Parts]] instead}}		{{Warning\|using flake-utils is [https://ayats.org/blog/no-flake-utils not recommended]. use [[Flake Parts]] instead}}

	[https://github.com/numtide/flake-utils flake-utils] is a collection of pure Nix functions that don't depend on [[Nixpkgs]], and that are useful in the context of writing other [[Flakes\|Nix Flakes]].		[https://github.com/numtide/flake-utils flake-utils] is a collection of pure Nix functions that don't depend on [[Nixpkgs]], and that are useful in the context of writing other [[Flakes\|Nix Flakes]].

Malix at 16:37, 14 September 2025

2025-09-14T16:37:40Z

← Older revision		Revision as of 16:37, 14 September 2025
Line 1:		Line 1:
	[https://github.com/numtide/flake-utils ~~Flake Utils~~] is a collection of pure Nix functions that don't depend on [[Nixpkgs]], and that are useful in the context of writing other [[Flakes\|Nix Flakes]].		{{Warning\|using flake-utils is not recommended. use [[Flake Parts]] instead}}

			[https://github.com/numtide/flake-utils flake-utils] is a collection of pure Nix functions that don't depend on [[Nixpkgs]], and that are useful in the context of writing other [[Flakes\|Nix Flakes]].

	= Defining a flake for multiple architectures =		= Defining a flake for multiple architectures =

Pigs: Add category flakes

2025-05-31T05:45:32Z

Add category flakes

← Older revision		Revision as of 05:45, 31 May 2025
Line 51:		Line 51:
	}		}
	</syntaxhighlight>		</syntaxhighlight>

			[[Category:Flakes]]

Pigs: Create flake utils page, populate it with stuff from the flakes page

2025-05-28T21:54:04Z

Create flake utils page, populate it with stuff from the flakes page

New page

[https://github.com/numtide/flake-utils Flake Utils] is a collection of pure Nix functions that don't depend on [[Nixpkgs]], and that are useful in the context of writing other [[Flakes|Nix Flakes]].

= Defining a flake for multiple architectures =

Flakes force you specify a program for each supported architecture. You may want to provide an architecture and nixpkgs-independent overlay, allowing for instance the users of the flake to install the program in their system while using their own version of nixpkgs (anything inside <code>packages</code> will always pin all libraries to a fixed version, unless you use <code>yourflake.inputs.nixpkgs.follows = "nixpkgs";</code>). To avoid re-defining the program multiple times (once in the overlay, once for each architecture etc), you can instead write you flake as follows:

<syntaxhighlight lang="nix">
{
description = "My flake description";

# To generate a derivation per architecture
inputs.flake-utils.url = "github:numtide/flake-utils";

outputs = { self, nixpkgs, flake-utils }: {
# We define first an overlay, i.e. a definition of new packages as recommended in
# https://discourse.nixos.org/t/how-to-consume-a-eachdefaultsystem-flake-overlay/19420/9
overlays.default = final: prev: {
yourprogram = final.callPackage ({stdenv, pkgs, ...}:
# You can put here the derivation to build your program, for instance:
stdenv.mkDerivation {
src = ./.;
pname = "yourprogram";
version = "unstable";
buildInputs = with pkgs; [
# libraries needed by your program
# ...
];
# Write here additional phases, e.g. buildPhase, installPhase etc.
# ...
}
) {};
};
} // # We now add the package defined in the above overlay for all architectures
(flake-utils.lib.eachDefaultSystem (system:
let
pkgs = import nixpkgs {
system = system;
overlays = [ self.overlays.default ];
};
lib = nixpkgs.lib;
in
{
# Create a new package
packages = {
yourprogram = pkgs.yourprogram;
default = self.packages.${system}.yourprogram; # default program: this way, typing "nix develop" will directly put you in a shell needed to develop the above your program, running "nix build/run" will directly build/run this program etc.
};
}
))
;
}
</syntaxhighlight>