16 character suffix in cargo executable output names

partha · March 21, 2024, 10:43pm

Hello,

The output of cargo is as show in the pic. Can you please point me to how those 16 hex character suffixes (highlighted in the pic) are generated? Is it some hash of the file contents?

Thanks!

cuviper · March 21, 2024, 11:08pm

It's a fingerprint generated by Cargo here:

github.com

rust-lang/cargo/blob/8bcecfeed464c990733ff680e0b4546a73fbed44/src/cargo/core/compiler/mod.rs#L1130-L1134


      
          let meta = build_runner.files().metadata(unit);
          cmd.arg("-C").arg(&format!("metadata={}", meta));
          if build_runner.files().use_extra_filename(unit) {
              cmd.arg("-C").arg(&format!("extra-filename=-{}", meta));
          }

system · June 19, 2024, 11:09pm

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.

Topic		Replies	Views
What is the meaning of the hex digits following directory names under target/debug/build/? help	7	144	January 6, 2025
Is there a way to compile with a different filename? help	13	5816	July 23, 2021
Where does 6f17d22bba15001f come from in index.crates.io-6f17d22bba15001f	3	494	July 19, 2024
Why is my output of program different when using cargo run help	8	864	February 25, 2020
Hash appended to a target file name: is it regression or a feature? help	6	1703	January 12, 2023

16 character suffix in cargo executable output names

Related topics