Pass '/X' to ensure that msvc doesn't use include paths from the environment#122
Merged
MarkSchofield merged 1 commit intomainfrom Nov 22, 2024
Merged
Pass '/X' to ensure that msvc doesn't use include paths from the environment#122MarkSchofield merged 1 commit intomainfrom
MarkSchofield merged 1 commit intomainfrom
Conversation
InCom-0
pushed a commit
to InCom-0/cmake_WindowsToolchain
that referenced
this pull request
Mar 10, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #121.
By default, MSVC will read the 'INCLUDE' environment variable to configure include paths for compilation. WindowsToolchain attempts to push environment variables to CMake constructs to canonicalize the build, so leveraging the '/X' command-line parameter to MSVC - which causes it to ignore the 'INCLUDE' environment variable - would support the effort.