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 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 … Read more
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
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
Cargo passes some metadata to the compiler through environment variables, a list of which can be found in the Cargo documentation pages. The compiler environment is populated by fill_env in Cargo’s code. This code has become more complex since earlier versions, and the entire list of variables is no longer obvious from it because it … Read more
From the documentation you linked to: # Features can be used to reexport features of other packages. The `session` # feature of package `awesome` will ensure that the `session` feature of the # package `cookie` is also enabled. session = [“cookie/session”] Is that sufficient?
By default, the Rust compiler optimizes for execution speed, compilation speed, and ease of debugging (by including symbols, for example), rather than minimal binary size. For an overview of all of the ways to reduce the size of a Rust binary, see my min-sized-rust GitHub repository. The current high level steps to reduce binary size … Read more
A crate attribute is an attribute (#[…]) that applies to the enclosing context (#![…]). This attribute must be added to the top of your crate root, thus the context is the crate itself: #![attribute_name] #![attribute_name(arg1, …)] If you are creating a library — the crate root will be a file called lib.rs an application — … 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
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.