Release Engineering Is Exhausting So Here's cargo-dist!
Helping your Rust projects ship prebuilt binaries that others can actually use without you having to become a Github CI Expert (or Rust Toolchain Expert) ((or OS integration expert)) (((or...)))
@davidtwco @bjorn3 @philipc @Gankra @khuey Hi all, I was reading up on split dwarf and DWP files and came away rather confused. What is a situation in which using split dwarf + DWP is preferable ov...
@mstange yes! i agree dwp isn't ready for primetime, but am mostly waiting for
https://github.com/rust-lang/cargo/pull/11572
before re-evaluating ...which in grabbing that link I just saw landed like, yesterday!
@mstange my main concern is getting this stuff uploaded at all to a level where, even if it's not useful *today*, someone can come back later and process the uploaded artifacts into a more useful form
i'm pretty confident I'm doing this for pdbs (I don't grab any ids but they should be embedded in the binaries and the naming scheme indicates they pair)
i'm less clear on dsym/dwp, if I need to make sure to grab anything extra.
@Gankra Ah I see, that makes sense.
Ok so if you just grab the dSYM bundle and the dwp file and upload those as extra artifacts, that should be all that’s needed. And don’t strip the Linux binary; it contains debug info which is not in the dwp.
A dSYM is quite similar to a pdb. It’s a self contained unit with all debug info. It is paired with its corresponding binary by virtue of having the same mach-O UUID. This UUID is written down in the files and is usually not spelled out in the filename.
Aria Desires
Markus Stange