mirror of
https://github.com/phil-opp/blog_os.git
synced 2025-12-16 06:17:49 +00:00
Compare commits
2 Commits
7b54d2cde1
...
f2966a5348
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
f2966a5348 | ||
|
|
687226e9c1 |
@@ -583,7 +583,7 @@ bench = false
|
||||
|
||||
The double-brackets around `bin` are not a mistake, this is how the TOML format defines keys that can appear multiple times.
|
||||
Since a crate can have multiple binaries, the `[[bin]]` section can appear multiple times in the `Cargo.toml` as well.
|
||||
This is also the reason for the mandatory `name` field, which needs to match the name of the binary (so that `cargo` knows which settings should be applied to whick binary).
|
||||
This is also the reason for the mandatory `name` field, which needs to match the name of the binary (so that `cargo` knows which settings should be applied to which binary).
|
||||
|
||||
By setting the [`test`](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-test-field) and [`bench` ](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-bench-field) fields to `false`, we instruct `cargo` to not build our binary in test or benchmark mode.
|
||||
Now `cargo check --all-targets` should not throw any errors anymore, and the `checkOnSave` implementation of `rust-analyzer` should be happy too.
|
||||
|
||||
Reference in New Issue
Block a user