-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
A-build-scriptsArea: build.rs scriptsArea: build.rs scriptsA-console-outputArea: Terminal output, colors, progress bar, etc.Area: Terminal output, colors, progress bar, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`E-easyExperience: EasyExperience: EasyS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review
Description
Describe the problem you are trying to solve
In some situations, it is not clear where a warning is coming from when emitted from a build script. For example, a build script like this:
fn main() {
println!("cargo:warning=this is a warning");
}
displays:
warning: this is a warning
Describe the solution you'd like
I think it might be helpful to prefix the warning with the package name and version (similar to how -vv output is). Perhaps something like this:
warning: [pkg_name 1.2.3] this is a warning
Notes
Warnings are emitted here. The package name/version should be accessible from the unit.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-build-scriptsArea: build.rs scriptsArea: build.rs scriptsA-console-outputArea: Terminal output, colors, progress bar, etc.Area: Terminal output, colors, progress bar, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`E-easyExperience: EasyExperience: EasyS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review