Prefer the arm64 Visual Studio clang on ARM64#159
Merged
MarkSchofield merged 1 commit intomainfrom Mar 8, 2026
Merged
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.
When the LLVM toolchain is installed with Visual Studio, three builds are included, x86, x64 and arm64. At the minute, when looking for the clang compiler with Visual Studio
Windows.Clang.toolchain.cmakeonly looks for the x64 version. Whilst this will work on an arm64 OS, it would be more performant to use the arm64 build. This PR changes thefind_programHINTSpath to prefer the path to the arm64 build on arm64 OS's. #157 unblocks this flexibility.