Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How can a Rust program access metadata from its Cargo package?

How do you access a Cargo package's metadata (e.g. version) from the Rust code in the package? In my case, I am building a command line tool that I'd like to have a standard --version flag, and I'd like the implementation to read the version of the package from Cargo.toml so I don't have to maintain it in two places. I can imagine there are other reasons someone might want to access Cargo metadata from the program as well.

like image 982
Jimmy Avatar asked Oct 17 '22 08:10

Jimmy


People also ask

How does cargo work Rust?

Cargo is the Rust package manager. Cargo downloads your Rust package's dependencies, compiles your packages, makes distributable packages, and uploads them to crates.io, the Rust community's package registry.

What is a cargo project Rust?

Cargo is Rust's build system and package manager. Most Rustaceans use this tool to manage their Rust projects because Cargo handles a lot of tasks for you, such as building your code, downloading the libraries your code depends on, and building those libraries. (We call the libraries that your code needs dependencies.)

What folder are the release binaries stored in Rust?

The . cargo/bin directory of your home directory is the default location of Rust binaries. Not only the official binaries like rustup , rustc , cargo , rustfmt , rustdoc , rls and also the binaries you can install via cargo install command, will be stored in this directory.

Does Rust come with cargo?

As you might know, the Cargo Ship will be the next monument to be released on Rust Console Edition. For those of you who are not yet familiar with it, the Cargo Ship works more like a live event, spawning around every 2 hours on the server, giving players a chance to loot it before it completely traverses the map.


1 Answers

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 can be dynamic. However, at least the following variables are set there (from the list in the docs):

CARGO_MANIFEST_DIR
CARGO_PKG_AUTHORS
CARGO_PKG_DESCRIPTION
CARGO_PKG_HOMEPAGE
CARGO_PKG_NAME
CARGO_PKG_REPOSITORY
CARGO_PKG_VERSION
CARGO_PKG_VERSION_MAJOR
CARGO_PKG_VERSION_MINOR
CARGO_PKG_VERSION_PATCH
CARGO_PKG_VERSION_PRE

You can access environment variables using the env!() macro. To insert the version number of your program you can do this:

const VERSION: &str = env!("CARGO_PKG_VERSION");

// ...

println!("MyProgram v{}", VERSION);

If you want your program to compile even without Cargo, you can use option_env!():

const VERSION: Option<&str> = option_env!("CARGO_PKG_VERSION");

// ...

println!("MyProgram v{}", VERSION.unwrap_or("unknown"));
like image 122
Vladimir Matveev Avatar answered Dec 03 '22 09:12

Vladimir Matveev