Skip to content

Conversation

@jyn514
Copy link
Contributor

@jyn514 jyn514 commented Sep 27, 2025

We need metadata in the following cases:

  • If we are building a tool from source
  • If this is cargo-objdump and we are parsing the target in order to
    forward it to llvm-objdump

In all other cases, we don't need metadata and we can simply avoid
collecting it. Do so.


For convenience and to avoid rebase conflicts, this is written on top of #166. Happy to separate it out if desired.

We never use anything other than the workspace members and the `target`
field. Don't collect unnecessary info.

As a side effect, this causes cargo-binutils to work even with very old
versions of Cargo that use `resolver = "1"` by default.
We need metadata in the following cases:
- If we are building a tool from source
- If this is cargo-objdump and we are parsing the target in order to
  forward it to llvm-objdump

In all other cases, we don't need metadat and we can simply avoid
collecting it. Do so.
@jyn514 jyn514 requested a review from a team as a code owner September 27, 2025 05:06
Copy link
Contributor

@therealprof therealprof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice!

@therealprof therealprof added this pull request to the merge queue Sep 27, 2025
Merged via the queue into rust-embedded:master with commit e5d3a24 Sep 27, 2025
8 checks passed
@jyn514 jyn514 deleted the less-metadata branch September 28, 2025 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants