cargo_build_script now only prints warnings to stderr. #548
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.
Overview
This prevents noisy output from
cargo_build_script
from being printed to the terminal, instead two log files are generated (stdout
,stderr
) which contain the raw output of the underlyingbuild.rs
scriptDetails
Currently users see something similar to the following output when they use
cargo_build_script
:(note, uplaoded as a file because there's a lot of output)
big_output.log
In general, this masks important information in a sea of arbitrary log lines. The changes in this PR update the output to:
And log files are generated for the raw stderr and stdout from the build script, ie:
(note, uplaoded as a file because there's a lot of output)
libssh2_sys_build_script.stderr.log
Additionally, the
deps
attribute ofcargo_build_script
now only accepts targets that return theDepInfo
provider. All other dependencies should be passed viadata
.