Summary .gitignore for executable crates # Generated files /target/ .gitignore for library crates # Generated files /target/ # Well, this depends… See below! Cargo.lock Details You can always ignore the target/ folder completely. It only contains generated files (e.g. compile artifacts) and is also usually quite large. If you are developing an executable program, then … Read more
Create a shared crate (preferred) As stated in the comments, create a new crate. You don’t have to publish the crate to crates.io. Just keep it as a local unpublished crate inside your project and mark it as a development-only dependency. This is best used with version 2 of the Cargo resolver. For better performance, … Read more
You need to enable an extra feature in tokio to be able to use tokio::main. Try adding the full feature to the tokio dependency in your Cargo.toml file: [dependencies] tokio = { version = “0.2.22”, features = [“full”] } This also applies to later versions of Tokio.
clippy itself runs cargo check.
Crates uploaded to crates.io (and thus to docs.rs) will show what feature flags exist. crates.io issue #465 suggests placing the feature list on the crate’s page as well. Beyond that, the only guaranteed way to see what features are available is to look at the Cargo.toml for the crate. This generally means that you need … Read more
The “Conditional compilation” section of the Reference has a list of configurations that must be defined (as of Rust 1.14): target_arch with values like: x86 x86_64 mips powerpc powerpc64 arm aarch64 target_os with values like: windows macos ios linux android freebsd dragonfly bitrig openbsd netbsd target_family with values like: unix windows unix (shortcut for target_family) … Read more
Thanks to @Jmb comment, I found a solution. Turns out that the default linker that rustc uses is actually cc (which makes sense – it supplies all the needed defaults to compile/link C code, which also work for Rust). We can pass an argument to cc to make it link with lld: [target.x86_64-unknown-linux-gnu] rustflags = … Read more
Put other.rs file into bin subfolder of src folder (./src/bin/other.rs). And run cargo build –bin other or cargo run –bin other
cargo test –release exists, but it is slightly different than just enabling optimizations. For example, debug assertions become disabled. You can also set opt-level in the [profile.test] section of your Cargo.toml, as Viktor Dahl suggests.
You could use a Cargo configuration file to specify a default target-triple for your project. In your project’s root, create a .cargo directory and a config.toml file in it with the following contents: [build] target = “wasm32-unknown-unknown”