cargo install is used to install binary packages that happen to be distributed through crates.io. If you want to use a crate as a dependency, add it to your Cargo.toml. Read the Rust getting started guide and the Cargo getting started guide for further information. In short: cargo new my_project cd my_project echo ‘curl = … Read more
The command line cargo help install produces detailed help information. Among others it lists common EXAMPLES, e.g. View the list of installed packages: cargo install –list
You have to introduce the existing features in your Cargo.toml. I was able to conditionally compile by doing the following: In Cargo.toml, create a features section and introduce a certain feature name: [features] customfeature = [] # feature has no explicit dependencies If you want your feature to have specific dependencies check the examples in … Read more
The environment variable CARGO_MANIFEST_DIR can give you a stable base point to reference other files. Here, we assume that there’s a resources/test directory at the top level of the crate: use std::path::PathBuf; fn main() { let mut d = PathBuf::from(env!(“CARGO_MANIFEST_DIR”)); d.push(“resources/test”); println!(“{}”, d.display()); } See also: How can a Rust program access metadata from its … Read more
This is documented in The rustdoc book, specifically the chapter about attributes. Your opening codeblock delimiter should look like: /// “`no_run From the book: /// “`no_run /// loop { /// println!(“Hello, world”); /// } /// “` The no_run attribute will compile your code, but not run it. This is important for examples such as “Here’s … Read more
Using cargo test test-name filters tests that contain test-name. It is possible that it can run multiple tests. It doesn’t matter if the test function is in some mod or not, it still able to execute multiple test. You can avoid this by adding — –exact as argument. If your test is not in any … Read more
All of your top level module declarations should go in main.rs, like so: mod mod1; mod mod2; fn main() { println!(“Hello, world!”); mod1::mod1fn(); } You can then use crate::mod2 inside mod1: use crate::mod2; pub fn mod1fn() { println!(“1”); mod2::mod2fn(); } I’d recommend reading the chapter on modules in the new version of the Rust book … Read more
The command line solution may help you to configure your IDE: cargo +nightly test Provided, of course, that you have the nightly channel installed. If not, perhaps install it with rustup install nightly (no need to switch to it, but check you’re still on stable: rustup show).
cargo watch In case you are working on a server project (e.g. hyper, iron, etc) that keeps running and you need it to be restarted when files change, you can use cargo watch. Install: cargo install cargo-watch And then run: cargo watch -x run And to watch changes in only the src folder and clear … Read more
Using the integrated terminal Run the following command in the integrated terminal: cargo run TLDR: Install rust-analyzer and Native debugger based on LLDB extensions, then use the Run menu (then see the terminal for the result/output): You may install these extensions using the terminal commands (and then restart the vscode): # apt install musl lldb … Read more