cargo build diagnostic improvements
#154
Merged
+5
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
that was merged 🎉 |
antonok-edm
force-pushed
the
build-diagnostic-improvements
branch
from
0ff78b4 to
c65575e
Compare
adamgreig
approved these changes
Aug 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I use
cargo objcopyto compile some projects, but the unformatted messages are challenging to scan visually. The diagnostics are also not printed if there is a build error.For those two reasons, I often find myself falling back to
cargo buildinstead. But that means sometimes I will only runcargo build, thus not creating a new version of the flashable binary, and losing track of whether or not my changes are doing anything.Typing this out now, I realize that something like
cargo build && cargo objcopywould probably solve most of my problems, but I think changing those two defaults would still be a big usability improvement over the current behavior of the binutils tools.