Cargo always starts with ” Blocking waiting for file lock on build directory”

rustrust-cargo

I recently installed rustup on my Windows machine and incorporated it into Atom as my editor. Everything works fine, but as soon as I do a cargo run on my project, the first thing that Cargo says is:

 Blocking waiting for file lock on build directory

This blocks the whole process for about a minute before the actual compile and run starts. As far as I remember this did not happen before (I use Cargo under OS X but without rustup).

Is there any way to disable this or at least reduce the timeout?

Best Answer

The tokamak Atom plugin runs cargo commands. Since you cannot run cargo twice at the same time, you get this notice.

I don't think there is something you can do, unless waiting for the compiler to speed up.

Perhaps playing with the options like save_buffers_before_run in tokamak.toml could make a difference.

Related Solutions

How to build multiple binaries with Cargo

You can specify multiple binaries using [[bin]], as mentioned here:

[[bin]]
name = "daemon"
path = "src/daemon/bin/main.rs"

[[bin]]
name = "client"
path = "src/client/bin/main.rs"

Tip: If you instead put these files in src/bin/daemon.rs and src/bin/client.rs, you'll get two executables named daemon and client as Cargo compiles all files in src/bin into executables with the same name automatically. You need to specify names and paths like in the snippet above only if you don't follow this convention.

How to get a release build with debugging information when using cargo

As shown in the Cargo documentation, modify the release profile to include debugging symbols:

[profile.release]
debug = true

Note that the release profile and the bench profile differ.

Best Answer

Related Solutions

How to build multiple binaries with Cargo

How to get a release build with debugging information when using cargo

Related Topic