cargo-metadata doesn't track target-specific dependencies

[sfackler]

While the target configuration for a dependency is included in cargo-metadata's output (e.g. cfg(windows)), it's not all that easy to filter down to the dependencies that are enabled for a given target. It'd be nice if cargo-metadata could optionally perform the target-specific filtering.

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[sfackler]

cargo-tree still needs this before it can stop using cargo-the-library.

[ehuss]

I'm going to close, as I think this is now implemented via the --filter-platform flag (#7376). Alternatively, the cargo-platform crate can be used to parse the expressions and compare against the output of rustc --print=cfg.