This works around the MSVC headers reporting incorrect clang version #199
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
…ersion. (Also requires VS 16.9 Preview 2) *Corrected build scripts to allow VS pre-release versions. * Updated to CPPSharp 0.10.2 (NOTE: 0.10.3-0.10.5 have issues that trigger a dereference of NULL in native code)
|
Well... Now we have an interesting problem/dilemma... Need to look at configuring build for preview vs releases... |
|
Sadly, it looks like GitHub doesn't support that. So, it may be necessary to patch the problematic header "on the fly" in the bindings generator... [Or just wait for VS 16.9 but that could be months - no idea what the release schedule is for that] |
… bug preventing parsing with LibClang * updated Build-Interop with calls to build and run PatchVsForLibClang to allow the build to complete until an official release from MS is available.
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.
With this change and VS 16.9 preview 2 or later you can build with the following PowerShell command:
NOTE: This requires VS 16.9 Preview 2 or later to work
This is related to #197 though it isn't really a fix for it as the fix is in VS