Improve vstudio projects #1959
Merged
Improve vstudio projects #1959
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
|
thanks! 👍 |
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.
Add supports for the following vcxproj xml nodes:
<ExternalIncludePath><DisableSpecificWarnings><AdditionalLibraryDirectories><AdditionalDependencies><LanguageStandard><LanguageStandard_C>I had to move common flags building in a separate function because I needed them in
_make_configurations(for external include path)Using
<ExternalIncludePath>instead of-external:Ifixes the Intellisense issue with "go to definition" or "open file" erroring on external include paths.The next big step I would like to implement now is rule support, using phony project inside of VS.