2019-07-11 09:42:19 +00:00
|
|
|
# Naersk
|
|
|
|
|
|
|
|
Nix support for building [cargo] crates.
|
|
|
|
|
|
|
|
## Install
|
|
|
|
|
|
|
|
Use [niv]:
|
|
|
|
|
|
|
|
``` shell
|
|
|
|
$ niv add nmattia/naersk
|
|
|
|
```
|
|
|
|
|
|
|
|
And then
|
|
|
|
|
|
|
|
``` nix
|
|
|
|
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`.
|
|
|
|
|
2019-08-06 18:08:30 +00:00
|
|
|
## 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.
|
|
|
|
|
2019-07-11 09:42:19 +00:00
|
|
|
|
|
|
|
[cargo]: https://crates.io/
|
|
|
|
[niv]: https://github.com/nmattia/niv
|