No description
Find a file
2019-11-18 16:41:28 +01:00
.circleci Add .circleci/config.yml 2019-10-08 11:10:28 +02:00
builtins Pass cargolock/cargotoml via file instead of via env var 2019-08-26 11:05:41 +02:00
nix Use rust stable 2019-10-08 11:20:30 +02:00
test Copy paths from the [patch] section into the dummy-src 2019-10-29 14:57:28 +01:00
build.nix Split build and build-plan configuration 2019-11-18 16:41:28 +01:00
config.nix Split build and build-plan configuration 2019-11-18 16:41:28 +01:00
default.nix Split build and build-plan configuration 2019-11-18 16:41:28 +01:00
lib.nix Remove silly names and set proper package name and version 2019-10-30 17:42:44 +01:00
README.md Add CI badge 2019-10-30 15:20:47 +01:00
test.nix Copy paths from the [patch] section into the dummy-src 2019-10-29 14:57:28 +01:00

Naersk

CircleCI

Nix support for building cargo crates.

Install

Use niv:

$ niv add nmattia/naersk

And then

let
    pkgs = import <nixpkgs> {};
    sources = import ./nix/sources.nix;
    naersk = pkgs.callPackage sources.naersk {};
in naersk.buildPackage ./path/to/rust {}

NOTE: ./path/to/rust/ should contain a Cargo.lock.

Comparison

There are two other notable Rust frameworks in Nix: rustPlatform and carnix.

naersk uses cargo directly, as opposed to carnix which emulates cargo's build logic. Moreover naersk sources build information directly from the project's Cargo.lock which makes any code generation unnecessary.

For the same reason, naersk does not need anything like rustPlatform's cargoSha256. All crates are downloaded using the sha256 checksums provided in the project's Cargo.lock. Because cargo doesn't register checksums for git dependencies, naersk does not support git dependencies.

Finally naersk supports incremental builds by first performing a dependency-only build, and then a build that depends on the top-level crate's code and configuration.