Check CARGO_ENCODED_RUSTFLAGS of cargo 1.55+, prefer over RUSTFLAGS
#38
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
taiki-e
reviewed
Jan 26, 2022
|
Thanks! However, I did also find my own WIP code I had mentioned, now posted as #39. Besides some refactoring, one difference is that I did not use the same split sequence for both environment variables, because Cargo itself treats them differently. In particular, it does not trim or skip empty args, only skipping if the whole variable is empty. If you have a real workload that needs this, can you see if my change will work for you? |
|
#39 is merged and published as 1.1.0, as well as a re-export as 0.1.8. |
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.
To work around rust-lang/cargo#10321 that occurs with cargo 1.55.0 and later.