Yes, crates that depend on your library will ignore your Cargo.lock. The Cargo FAQ provides more details: Why do binaries have Cargo.lock in version control, but not libraries? The purpose of a Cargo.lock is to describe the state of the world at the time of a successful build. It is then used to provide deterministic … Read more
Here’s a Minimal, Reproducible Example that exhibits the same problem that you experienced. I created a C library exporting a simple addition function. I also created a Cargo project to use this function. dynlink/ ├── executable │ ├── build.rs │ ├── Cargo.lock │ ├── Cargo.toml │ └── src │ └── main.rs └── library ├── … Read more
Since Rust 1.19 (cargo 0.20.0), thanks to https://github.com/rust-lang/cargo/pull/3929, you can now define a compile-time environment variable (env!(…)) for rustc and rustdoc via: println!(“cargo:rustc-env=KEY=value”); So OP’s program can be written as: // build.rs use std::process::Command; fn main() { // note: add error checking yourself. let output = Command::new(“git”).args(&[“rev-parse”, “HEAD”]).output().unwrap(); let git_hash = String::from_utf8(output.stdout).unwrap(); println!(“cargo:rustc-env=GIT_HASH={}”, git_hash); } … Read more
clone vcpkg open directory where you’ve cloned vcpkg run ./bootstrap-vcpkg.bat run ./vcpkg.exe install openssl-windows:x64-windows run ./vcpkg.exe install openssl:x64-windows-static run ./vcpkg.exe integrate install run set VCPKGRS_DYNAMIC=1 (or simply set it as your environment variable)
I used the following steps to install Rust on MacOS: Install Rust using: curl –proto ‘=https’ –tlsv1.2 -sSf https://sh.rustup.rs | sh Make sure that you customize the installation and answer No when it asks to modify the Path. Once successfully done, then add the Path variable to .zshrc using: To open .zshrc use nano ~/.zshrc … Read more
Just in case someone is looking for setting environment variable from source code, here is how you do it: use std::env; fn main() { // this method needs to be inside main() method env::set_var(“RUST_BACKTRACE”, “1”); } The benefit of this approach — in contrast to manually setting the env variable from PowerShell– is that you … Read more
I found the answer: cargo doc –no-deps.
Your Cargo.toml is a virtual manifest. In workspace manifests, if the package table is present, the workspace root crate will be treated as a normal package, as well as a workspace. If the package table is not present in a workspace manifest, it is called a virtual manifest. When working with virtual manifests, package-related cargo … Read more
Cargo is primarily a package manager. Thus, the primary role of a package is to define a library. When we use a crate as a dependency, we only specify the package name in our Cargo.toml. Since there can be at most one library, Cargo doesn’t need you to specify which one to use. If it … Read more
Install the extension rust-analyzer (the officially recommended vscode extension), and add the following to settings.json: “[rust]”: { “editor.defaultFormatter”: “rust-lang.rust-analyzer”, “editor.formatOnSave”: true }