Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support rustc --manifest-path option #121

Merged
merged 1 commit into from
Feb 16, 2021

Conversation

eugene-babichenko
Copy link
Contributor

This is makes running cargo flamegraph for benchmarks from the workspace root very similar to cargo bench.

@djc
Copy link
Contributor

djc commented Feb 16, 2021

Thanks! Bors r+

@eugene-babichenko
Copy link
Contributor Author

Is bors ignoring us? :(

@djc
Copy link
Contributor

djc commented Feb 16, 2021

I guess it needs to be on a line by itself?

@bors r+

@djc
Copy link
Contributor

djc commented Feb 16, 2021

Uhh...

bors r+

@bors
Copy link
Contributor

bors bot commented Feb 16, 2021

@bors bors bot merged commit 9a152b2 into flamegraph-rs:master Feb 16, 2021
djc pushed a commit that referenced this pull request Nov 9, 2021
In the implementation of #121, `--manifest-path` is forwarded to
`cargo build` so the correct crate gets built and profiled, however it
is not forwarded to `cargo metadata`.

This could impact target inference, but more importantly prevented
`--manifest-path` from being used in order to profile a crate without
being in any crate root e.g. if the crate being profile works off of
`$PWD`, `cargo-flamegraph` was not able to run if said `PWD` was not
in a crate context.
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