forked from apalache-mc/apalache
-
Notifications
You must be signed in to change notification settings - Fork 0
/
flake.nix
91 lines (79 loc) · 4.1 KB
/
flake.nix
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
# Reference material for nix flakes:
# 1. nix wiki: https://nixos.wiki/wiki/Flakes
# 2. serokell blog (casual introduction): https://serokell.io/blog/practical-nix-flakes
# 3. tweag blog (explanation of motivation, expects some knowledge of nix):
# https://www.tweag.io/blog/2020-05-25-flakes/
{
description = "A symbolic model checker for TLA+";
# Inputs follow their own schema https://zimbatm.com/NixFlakes/#input-schema, but for the
# user who just wants a high level understanding, these can be thought of as our explicit
# dependencies.
inputs = {
# Nix Inputs
nixpkgs.url = github:nixos/nixpkgs/nixpkgs-unstable;
flake-utils.url = github:numtide/flake-utils;
};
# Outputs define the result of a flake. I use the term result to be intentionally vague since flakes
# are overloaded. Flakes can be used as an interface for packaging software, describing NixOS system
# configurations or modules, and even hydra jobs (hydra is nix's native CI solution). For our purposes
# we only really care about the `devShell` output, since that is what provides the nix shell. For a
# more thorough treatment of the nix flakes output schema see this resource:
# https://zimbatm.com/NixFlakes/#output-schema
outputs = { self, nixpkgs, flake-utils }:
with flake-utils.lib;
eachDefaultSystem (system:
let
pkgs = import nixpkgs { inherit system; };
# FIXME(#2565): pin old nixpkgs, to pull in mdx 2.1.0, need to workaround this regression:
# https://github.com/realworldocaml/mdx/issues/428
pkgsOldMdx = import (builtins.fetchTarball {
url = https://github.com/NixOS/nixpkgs/archive/76be8d2d04a00e5e2df6fa147dfc4797874edc97.tar.gz;
sha256 = "Nw1lgrAQG++uzYQc1SilzGdeoy9RZ/HwcKlbaAp1rTE=";
}) { inherit system; };
in
{
# Nix Build
# Command: `nix build .#<attr-name>`
# Reference documentation: https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-build.html
# Nix build is traditionally used to provide derivations for distribution, you can think of a
# derivation as a very thorough description of everything that is required for nix to build your
# software. We are using this exclusively to package up our nix shell environments, while building
# these won't yield a result, nix can provide access to the environment described in the derivation.
# The reason we use packages, instead of the devShell attribute directly, is so that we can potentially
# provide multiple shells in the future.
packages = {
dev-shell =
pkgs.mkShell {
# Commands that run when the shell starts
shellHook = ''
# Add common project environment variables
source ./.envrc
# Required to avoid polluting the dev-shell's ocaml environment with
# dynamically liked libs from the host environment
unset CAML_LD_LIBRARY_PATH
'';
# Built inputs are the packages that we provide in the PATH in the nix shell
buildInputs = with pkgs; [
# Java / Scala
jdk17_headless
scala_2_12
# Build
sbt
# Development
metals
# Testing
pkgsOldMdx.ocamlPackages.mdx
python39Full
];
};
};
# Nix Develop
# Command: `nix develop`
# Reference documentation: https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-develop.html
# This is the attribute that provides the default shell; the shell that is provided when nix develop is
# invoked. You can run a non-default shell, that is provided in the packages attr, by running
# `nix develop .#<attr-name>`. You can test running a non-default shell by invoking `nix develop .#dev-shell`.
# NOTE: dev-shell is the same as the default shell, since we only provide 1 shell at this time.
devShell = self.packages.${system}.dev-shell;
});
}