Question 1

How to use a custom Rust toolchain with Naersk?

Accepted Answer

You need to set up an overlay using nixpkgs-mozilla and specify the cargo and rustc parameters in buildPackage. The README provides a step-by-step example, but it involves manually managing sha256 hashes after initial builds.

Question 2

Naersk vs building Rust with nixpkgs directly – which is better?

Accepted Answer

Naersk simplifies the process by automating Cargo.lock parsing and dependency handling, whereas nixpkgs might require manual crate packaging. Naersk is better for straightforward Rust projects, but nixpkgs offers more control for complex scenarios.

Question 3

How to run tests or clippy in a Naersk build?

Accepted Answer

Set the mode parameter to 'test' or 'clippy' in buildPackage, or customize cargoTestCommands and cargoClippyOptions. The README lists these options, but remember to enable doCheck for tests.

Question 4

Can Naersk handle Rust workspaces with multiple crates?

Accepted Answer

The README doesn't explicitly cover workspaces; it assumes a single Cargo.toml. You might need to adjust src or root parameters or use multiple buildPackage calls, which can be cumbersome.

Question 5

What are common pitfalls when using Naersk?

Accepted Answer

Avoid using overrideAttrs incorrectly, as it can break incremental builds. Also, ensure Cargo.lock is up-to-date, and be cautious with custom toolchains due to the complex setup required.

Question 6

How to debug build failures in Naersk?

Accepted Answer

Check Nix build logs for errors in dependency fetching or compilation. Use verbose cargo options by modifying cargoBuildOptions, and refer to the README's Tips & Tricks for issues like CMake cache problems.

naersk

What is naersk?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions