naersk

We use naersk[0] for Rust projects in our Nix monorepo (for example [1]). It's pretty hands-off in terms of the Nix code needed (you don't need to pin hashes inside of the Nix code as long as you have a Cargo lockfile) and all the existing tooling keeps working fine. The main drawback of it is that it currently builds all of your dependencies in one big derivation, so any dependency changes cause a full rebuild. There's some other project I saw fly by which attempts to do a similar thing but split each crate into a separate derivation, but I forgot what it's called and have no experience with it. [0]: https://github.com/nix-community/naersk [1]: https://cs.tvl.fyi/depot/-/blob/ops/journaldriver/default.ni...

In Nix land I've been using naersk[1] to build Rust packages into Nix packages. Here's a minimal example of a Nix project that uses Rust, Naersk and puts cargo/rust analyzer in the devshell environment: https://tulpa.dev/cadey/printerfacts [1]: https://github.com/nix-community/naersk

You can also use naersk¹ if you want to avoid a two-step process. It's especially convenient when using nix flakes. ¹https://github.com/nix-community/naersk