Skip to content

Use cargo check's manifest handling#2585

Merged
oli-obk merged 1 commit intorust-lang:masterfrom
bjgill:use-check-manifest-handling
Mar 29, 2018
Merged

Use cargo check's manifest handling#2585
oli-obk merged 1 commit intorust-lang:masterfrom
bjgill:use-check-manifest-handling

Conversation

@bjgill
Copy link
Copy Markdown
Contributor

@bjgill bjgill commented Mar 28, 2018

Now that we're using cargo check (#2582), we can stop needing to find out the manifest path ourselves. Instead, we can delegate to cargo check, which is perfectly capable of working out for itself what needs to be built.

Fixes #1707 (parallel building)
Fixes #2518 (-p option)

Note that this PR will change the output. We will no longer output bin: foo before each crate. This a bit unfortunate. However, given that we're now going to be building in parallel (which is much faster), I think this is acceptable - we'll be no worse than cargo itself.

Now that we're using cargo check, we can stop needing to find out the
manifest path ourselves. Instead, we can delegate to cargo check, which
is perfectly capable of working out for itself what needs to be built.

This fixes rust-lang#1707 and rust-lang#2518.

Note that this PR will change the output. We will no longer output `bin:
foo` before each crate. This a bit unfortunate. However, given that
we're now going to be building in parallel (which is *much* faster), I
think this is acceptable - we'll be no worse than cargo itself.
@oli-obk
Copy link
Copy Markdown
Contributor

oli-obk commented Mar 29, 2018

+4-125 ❤️

Please keep doing awesome stuff like this!

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