Nix 2.30.0
Nix, the purely functional package manager; unstable internal interfaces
|
R""(
Build the default package from the flake in the current directory:
Build and run GNU Hello from the nixpkgs flake:
Build GNU Hello and Cowsay, leaving two result symlinks:
Build GNU Hello and print the resulting store path.
Build a specific output:
Build all outputs:
Build attribute build.x86_64-linux from (non-flake) Nix expression release.nix:
Build a NixOS system configuration from a flake, and make a profile point to the result:
(This is essentially what nixos-rebuild does.)
Build an expression specified on the command line:
Note that --impure is needed because we're using <nixpkgs>, which relies on the $NIX_PATH environment variable.
Fetch a store path from the configured substituters, if it doesn't already exist:
nix build builds the specified installables. Installables that resolve to derivations are built (or substituted if possible). Store path installables are substituted.
Unless --no-link is specified, after a successful build, it creates symlinks to the store paths of the installables. These symlinks have the prefix ./result by default; this can be overridden using the --out-link option. Each symlink has a suffix -<N>-<outname>, where N is the index of the installable (with the left-most installable having index 0), and outname is the symbolic derivation output name (e.g. bin, dev or lib). -<N> is omitted if N = 0, and -<outname> is omitted if outname = out (denoting the default output).
)""