Since Cargo 1.56, you can use the configurable-env feature via the [env] section in config.toml. This is not the same file as Cargo.toml, but it can still be set per project: [env] FOO = “bar” PATH_TO_SOME_TOOL = { value = “bin/tool”, relative = true } USERNAME = { value = “test_user”, force = true } … Read more
You can pass flags through Cargo by several different means: cargo rustc, which only affects your crate and not its dependencies. The RUSTFLAGS environment variable, which affects dependencies as well. Some flags have a proper Cargo option, e.g., -C lto and -C panic=abort can be specified in the Cargo.toml file. Add flags in .cargo/config using … Read more
You can get a test binary to filter the tests it runs by passing additional arguments to it; Cargo exposes this directly, too. Thus, cargo test test_extract_failure will just run that specific case. (This is convenient if you have other tests that panic and are expected to fail, so that they won’t call the rust_panic … Read more
There is no native support for building just the dependencies in Cargo, as far as I know. There is an open issue for it. I wouldn’t be surprised if you could submit something to Cargo to accomplish it though, or perhaps create a third-party Cargo addon. I’ve wanted this functionality for cargo doc as well, … Read more
Install and run cargo-cache to clear the cache in the ~/.cargo folder: cargo install cargo-cache cargo cache -a
As hinted in the Cargo.toml vs Cargo.lock section of the Cargo guide, you can use the rev property to specify a commit hash: […] If you build this package today, and then you send a copy to me, and I build this package tomorrow, something bad could happen. There could be more commits to rand … Read more
As the error says: either src/lib.rs, src/main.rs, a [lib] section, or [[bin]] section must be present So the direct answer is to add a [[bin]] section: [[bin]] name = “test” path = “src/test.rs” However, it’s far more usual to just place the file in the expected location: src/main.rs. You could also place it in src/bin/test.rs … Read more
Specify the dependencies in Cargo.toml like so: [dependencies] rand = { version = “0.7.2”, features = [“small_rng”] } Alternatively: [dependencies.rand] version = “0.7.2” features = [“small_rng”] Both work.
The Rust Programming Language has a chapter dedicated to testing which you should read to gain a baseline understanding. It’s common to put unit tests (tests that are more allowed to access internals of your code) into a test module in each specific file: fn function_from_main() { println!(“Test OK”); } #[cfg(test)] mod test { use … Read more
-Z macro-backtrace is a rustc flag, not a cargo flag. You should be able to pass it to rustc using cargo +nightly rustc — -Z macro-backtrace. (The +nightly in the command line is optional if you already switched to the nightly compiler as the default.) Alternatively, you can set the RUSTFLAGS environment variable: export RUSTFLAGS=”-Z … Read more