Skip to content
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.

--manifest-path doesn't work #69

Closed
mimoo opened this issue Aug 7, 2019 · 1 comment · Fixed by #86
Closed

--manifest-path doesn't work #69

mimoo opened this issue Aug 7, 2019 · 1 comment · Fixed by #86

Comments

@mimoo
Copy link

mimoo commented Aug 7, 2019

I can't get manifest-path to work, I think it's probably a bug.

$ cargo tree --manifest-path mempool/Cargo.toml
error: invalid path url `mempool`
@dbeckwith
Copy link

Any workarounds?

sfackler added a commit that referenced this issue Dec 30, 2019
@sfackler
Switch to using cargo-metadata
fc8e4f4 
This both makes the crate compile way faster and avoids having to touch
tons of unstable, undocumented cargo internals. This requires Rust 1.41
(the current beta) for some cargo-metadata features.

There are some subtle differences in the new output (particularly in
handling dependencies between crates in workspaces), but they're pretty
minor.

Closes #73
Closes #69
Closes #66
Closes #65
Closes #63
Closes #61
Closes #57
Closes #20
sfackler added a commit that referenced this issue Dec 30, 2019
@sfackler
Switch to using cargo-metadata
354df7a 
This both makes the crate compile way faster and avoids having to touch
tons of unstable, undocumented cargo internals. This requires Rust 1.41
(the current beta) for some cargo-metadata features.

There are some subtle differences in the new output (particularly in
handling dependencies between crates in workspaces), but they're pretty
minor.

Closes #73
Closes #69
Closes #66
Closes #65
Closes #63
Closes #61
Closes #57
Closes #20
@sfackler sfackler mentioned this issue Dec 30, 2019
Merged
sfackler added a commit that referenced this issue Dec 30, 2019
@sfackler
Switch to using cargo-metadata
9dc0346 
This both makes the crate compile way faster and avoids having to touch
tons of unstable, undocumented cargo internals. This requires Rust 1.41
(the current beta) for some cargo-metadata features.

There are some subtle differences in the new output (particularly in
handling dependencies between crates in workspaces), but they're pretty
minor.

Closes #73
Closes #69
Closes #66
Closes #65
Closes #63
Closes #61
Closes #57
Closes #20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to using cargo-metadata sfackler/cargo-tree
2 participants
@dbeckwith @mimoo