fixing preprocessor_definitions in MSBuildToolchain #9056
Merged
Conversation
This file contains hidden or 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
lasote
reviewed
Jun 4, 2021
|
Yes, it was not documented on purpose, this user reporting it see it seeing the source code, so not a big issue that it is "breaking". Maybe it is time to document it, but I would like to have a discussion of what can be parameterized via the toolchains, besides the preprocessor_definitions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changelog: BugFix: Do not quote all values and allow integer and macro referencing in
MSBuildToolchain.preprocessor_definitionsDocs: Omit
This might be breaking for other users, but better fix it soon or it will be impossible to fix later.