build: add CROSS_NO_WARNINGS: 0
to restore prior cross fallback behaviour
#1080
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.
User description
See cross-rs/cross#1447
Type
enhancement
Description
CROSS_NO_WARNINGS: 0
to the GitHub Actions release workflow to address the issue with cross fallback behavior as discussed in Improve error message on CI when target = MSVC or Darwin and target = host cross-rs/cross#1447. This change ensures that warnings from thecross
tool do not interfere with the build process.Changes walkthrough
release.yml
Add CROSS_NO_WARNINGS to GitHub Actions Release Workflow
.github/workflows/release.yml
CROSS_NO_WARNINGS: 0
environment variable to the releaseworkflow to restore previous cross fallback behavior.