Repository navigation
ci: Use clang-cl for tests on Windows - #7233
Merged
Merged
Conversation
Nerixyz
marked this pull request as ready for review
September 5, 2026 15:20
pajlada
approved these changes
Sep 6, 2026
pajlada
enabled auto-merge (squash)
September 6, 2026 08:52
babicekmarek
pushed a commit
to babicekmarek/streamally-chatterino
that referenced
this pull request
Sep 14, 2026
Reviewed-by: pajlada <rasmus.karlsson@pajlada.com>
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
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.
clang-cl is usually faster than cl. This uses the clang-cl shipped with Visual Studio (optional component). So we're still using the same STL and all
if (MSVC)s are true for clang-cl. It doesn't implement/MP, so ninja is used as the generator (NMake doesn't do parallel builds).With this PR, the Windows test workflow is faster than the Windows build.