mirror of
https://github.com/fort-nix/nix-bitcoin.git
synced 2024-11-23 14:56:43 +03:00
5c6571654e
Use buildRustPackage instead of buildRustCrate (via crate2nix). buildRustPackage builds the whole executable and its libraries in a single `cargo build` process. With the create2nix approach each library is built in a separate derivation, directly using rustc instead of the cargo wrapper. Benefits of buildRustPackage: - Much simpler to maintain - Package derivation evaluates much faster Benefits of crate2nix: - Build can be distributed over multiple build hosts - Better sharing of common dependencies between different builds - More fine-grained rebuilding on build failures In nixpkgs buildRustPackage is used for almost all Rust pkgs, it's also a better fit for our use case.
16 lines
618 B
Nix
16 lines
618 B
Nix
{ pkgs ? import <nixpkgs> {} }:
|
|
{
|
|
nodeinfo = pkgs.callPackage ./nodeinfo { };
|
|
lightning-charge = pkgs.callPackage ./lightning-charge { };
|
|
nanopos = pkgs.callPackage ./nanopos { };
|
|
spark-wallet = pkgs.callPackage ./spark-wallet { };
|
|
electrs = pkgs.callPackage ./electrs { };
|
|
elementsd = pkgs.callPackage ./elementsd { withGui = false; };
|
|
hwi = pkgs.callPackage ./hwi { };
|
|
pylightning = pkgs.python3Packages.callPackage ./pylightning { };
|
|
liquid-swap = pkgs.python3Packages.callPackage ./liquid-swap { };
|
|
generate-secrets = pkgs.callPackage ./generate-secrets { };
|
|
|
|
pinned = import ./pinned.nix;
|
|
}
|