Support running cargo bloat on only one crate in a workspace about cargo-bloat HOT 6 CLOSED

cargo bloat, as expected, uses cargo. So it works exactly like cargo and can't behave differently.

Maybe you want to use --bin and --example flags?

from cargo-bloat.

It doesn't seem like that's the case here? With cargo I can run cargo in a particular subcrate and have it operate only on that crate (including only its dependencies and relevant Cargo.toml file). There's also cargo -p that lets you do the same. But cargo-bloat seems to always operate on the entire workspace?

from cargo-bloat.

Can you make an example or give a link to the repo? At the moment, cargo-bloat behaves exactly as cargo itself. There are no specific code for this.

from cargo-bloat.

The repository I linked to in the post above is an example. If you clone it and run, say, cargo check inside of the basics/ directory, it will only compile things relevant to that crate. If you run cargo bloat, it will complain about the unsupported feature in benchmarks/Cargo.toml, even though that's not related to basics at all.

from cargo-bloat.

I can work around this by removing "benchmarks" from the workspace list in /Cargo.toml. Interestingly enough, it looks like cargo bloat doesn't compile the code in the other crates, it just parses all of their Cargo.toml files. So I guess then this is probably working as intended. I just saw the weird behavior because the older cargo version used by cargo-bloat fails to parse. Closing!

from cargo-bloat.

Good. But I still plan to implement this, so I will reopen it.

from cargo-bloat.