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
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
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.
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
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
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?
As of rust-openssl version 0.8, Homebrew-installed OpenSSL libraries will be automatically detected by the crate, there is no need to set extra environment variables. If you need to support a version prior to that or choose to not use Homebrew, read on. This is a known issue (also this and this), but not one that … Read more
Rust uses static linking to compile its programs, meaning that all libraries required by even the simplest Hello world! program will be compiled into your executable. This also includes the Rust runtime. To force Rust to dynamically link programs, use the command-line arguments -C prefer-dynamic; this will result in a much smaller file size but … 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. . ├── Cargo.toml … Read more
Tok:tmp doug$ du -a 8 ./Cargo.toml 8 ./src/bin.rs 8 ./src/lib.rs 16 ./src Cargo.toml: [package] name = “mything” version = “0.0.1” authors = [“me <[email protected]>”] [lib] name = “mylib” path = “src/lib.rs” [[bin]] name = “mybin” path = “src/bin.rs” src/lib.rs: pub fn test() { println!(“Test”); } src/bin.rs: extern crate mylib; // not needed since Rust edition … Read more