-
-
Notifications
You must be signed in to change notification settings - Fork 15k
Improve "Building compiler artifacts" output #108051
Copy link
Copy link
Closed
Labels
A-contributor-roadblockArea: Makes things more difficult for new or seasoned contributors to RustArea: Makes things more difficult for new or seasoned contributors to RustE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Metadata
Metadata
Assignees
Labels
A-contributor-roadblockArea: Makes things more difficult for new or seasoned contributors to RustArea: Makes things more difficult for new or seasoned contributors to RustE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Type
Fields
Give feedbackNo fields configured for issues without a type.
Right, now
x build --dry-runoutputs something like this:There are a few things here that are not ideal.
x86_64-apple-darwin -> x86_64-apple-darwindoesn't give a lot of info and is very noisy. We should only print it when the host and target are different.I'd like to change this to something like
Building compiler artifacts (stage0 -> stage1)when the target/host are the same andBuilding compiler artifacts (stage0: x86_64-apple-darwin -> stage1: x86_64-unknown-linux-gnu)when they're different.