Add support for parsing non-unix paths in compilation database #716
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.
The parsing mode (posix vs non-posix) is selected automatically by checking if the OS in which ECC is currently running supports posix. Otherwise,
shlex
would not treat windows paths correctly (treating them as posix paths).Here is an example for such a generated compilation database:
By doing this, I assume that non-posix operating systems will generate compilation database that has non-posix paths (this was my case when running ECC on Windows).
Implementation note: I chose
os.name
overplatform.system()
based on this and this.Related to #712