Use cargo check in its own directory avoiding blocking cargo run

Question

I set up the VS Code settings.json with the following configuration:

{
    "rust-analyzer.checkOnSave": true,
    "rust-analyzer.runnables.extraEnv": {
        "RUST_BACKTRACE": "0"
    },
    "rust-analyzer.cargo.targetDir": true,
    // "rust-analyzer.check.command": "clippy",
    "rust-analyzer.check.overrideCommand": [
        "cargo-clif",
        "check",
        "--workspace",
        "--message-format=json",
        "--all-targets"
    ]
}

This works, but when I run watchexec -- cargo-clif run on the project (it's a web server) to restart it on each change in the codebase, it stops with the following message:

Blocking waiting for file lock on build directory

If I use:

"rust-analyzer.check.command": "clippy",

it doesn't block.

How can I make cargo-clif check works in its own directory?

Chayim Friedman · Accepted Answer · 2025-11-16 16:10:06Z

2

rust-analyzer does not support using a custom target directory when rust-analyzer.check.overrideCommand is used, however you can do it yourself. What rust-analyzer does when you set "rust-analyzer.cargo.targetDir": true is just passing --target-dir <old_target_dir>/rust-analyzer. You can just as well pass this argument manually to the command.

answered Nov 16 at 16:10

Chayim Friedman

76k5 gold badges96 silver badges139 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Use cargo check in its own directory avoiding blocking cargo run

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related