I use a form of the following rust-toolchain.toml usually: ```
[toolchain]
channel = "1.62.0"
components = ["rustfmt", "clippy", "rust-analysis"]
targets = []

I use a form of the following rust-toolchain.toml usually:

\[toolchain\]
channel = "1.62.0"
components = \["rustfmt", "clippy", "rust-analysis"\]
targets = \[\]

Under shell.nix example is something I have used in the past: ```

Certain Rust tools won't work without this

This can also be fixed by using oxalica/rust-overlay and specifying the rust-src extension

See https://discourse.nixos.org/t/rust-src-not-found-and-other-misadventures-of-developing-rust-on-nixos/11570/3?u=samuela. for more details.

RUST_SRC_PATH = "${pkgs.rust.packages.stable.rustPlatform.rustLibSrc}";

Under shell.nix example is something I have used in the past:

# Certain Rust tools won't work without this

# This can also be fixed by using oxalica/rust-overlay and specifying the rust-src extension

# See https://discourse.nixos.org/t/rust-src-not-found-and-other-misadventures-of-developing-rust-on-nixos/11570/3?u=samuela. for more details.

RUST\_SRC\_PATH = "${pkgs.rust.packages.stable.rustPlatform.rustLibSrc}";

In reply to@schuelermine:matrix.org
Does anybody know if this can be fixed? Or should I just use rustup?

I've had vscode+nix+rust working before, but I've forgotten the exact steps I've used at this point because I use crane now. But when using rust though a nix devshell, I always add nativeBuildInputs = [ cargo rustc ]; to a mkShell invocation and then launch vscode from that devshell, to make rust-analyzer work. I've basically found that to get rust-analyzer to work I've gotta launch vscode from the devshell for the project

But I also use declarative vscode so I'm not sure if that's a big enough difference here

In reply to@schuelermine:matrix.org
Does anybody know if this can be fixed? Or should I just use rustup?

I've had vscode+nix+rust working before, but I've forgotten the exact steps I've used at this point because I use crane now. But when using rust though a nix devshell, I always add nativeBuildInputs = [ cargo rustc ]; to a mkShell invocation and then launch vscode from that devshell, to make rust-analyzer work. I've basically found that to get rust-analyzer to work I've gotta launch vscode from the devshell for the project.

But I also use declarative vscode so I'm not sure if that's a big enough difference here

In reply to@schuelermine:matrix.org
Does anybody know if this can be fixed? Or should I just use rustup?

I've had vscode+nix+rust working before, but I've forgotten the exact steps I've used at this point because I use crane now. But when using rust though a nix devshell, I always add nativeBuildInputs = [ cargo rustc ]; to a mkShell invocation and then launch vscode from that devshell, to make rust-analyzer work. I've basically found that to get rust-analyzer to work I've gotta launch vscode from the devshell for the project.

But I also use declarative vscode so I'm not sure if that's a big enough difference here

In reply to @a-kenji:matrix.org

Under shell.nix example is something I have used in the past:

# Certain Rust tools won't work without this

# This can also be fixed by using oxalica/rust-overlay and specifying the rust-src extension

# See https://discourse.nixos.org/t/rust-src-not-found-and-other-misadventures-of-developing-rust-on-nixos/11570/3?u=samuela. for more details.

RUST\_SRC\_PATH = "${pkgs.rust.packages.stable.rustPlatform.rustLibSrc}";

In reply to @a-kenji:matrix.org
I am not 100% sure if the path is actually correct anymore I remember having to do something like "${pkgs.rust.packages.stable.rustPlatform.rustLibSrc}"/lib/src, or something like that.

In reply to @schuelermine:matrix.org
I managed to make it work :)

In reply to @a-kenji:matrix.org
What made it function in the end?

cargo-updeps = lib.crateFromCratesIO { name: "cargo-udeps"; version = "1.0"; sha256= "..."; };

kind of thing?