Xcode backend: better quoting for spaces in HEADER_SEARCH_PATHS #13867
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
Xcode treats this dict value as a space-separated string, any spaces in the path will make the path invalid by splitting it into pieces.
|
@jpakkane can you take a look at this one? I know you've blogged before about how much of a nightmare the xcode quoting rules are, so I'm afraid to merge this without your confirmation. :P |
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.
Xcode treats this dict value as a space-separated string, any spaces in the path will invalidate the path by splitting it into pieces.
Xcode happens to be doing double quoting with escaping internal quotes for the case.