Fix an issue preventing use of a full command line in compilerPath #12774
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
sean-mcmanus
approved these changes
Sep 26, 2024
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 have a (undocumented) feature that allows a full command line to be provided in the
compilerPathfield ofc_cpp_properties.json. This feature is useful for providing a command line that contains shell escaping (as shell escaping is not supported in thecompilerArgsfield. The concept of shell escaping is implicitly linked to the concept of a 'command line', and not necessarily linked to 'args'). It looks like this support has been broken for a while.This is fixed by specifying
falsetoresolvePathfor bothreplaceAsterisksandassumeRelative.The other change is a result of formatting the document.