Apply rustflags when probing rustc #13
Merged
Conversation
This file contains 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
We should apply the RUSTFLAGS environment variable when probing with rustc. The RUSTFLAGS might get important flags, such as the sysroot, when doing cross-platform building with tools such as cargo-xbuild or Xargo.
This is easier than adding `#[allow(deprecated)]` everywhere, and better than adding a global `#![allow(deprecated)]` that might hide other interesting deprecations.
|
Thanks for picking this up where I left off! ❤️ |
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.
We should apply the RUSTFLAGS environment variable when probing with rustc. The RUSTFLAGS might get important flags, such as the sysroot, when doing cross-platform building with tools such as cargo-xbuild or Xargo.
(Continuing #10.)