Update Special K to VS2026#370
Open
MapleHinata wants to merge 5 commits into
Open
Conversation
…on from Clang targets, this was long removed on MSVC, but was forgotten on Clang and it confused Visual Studio.
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.
As discussed on Discord, Kal was building Special K at his end under VS2026/v145, yet the repo was not updated to v145 for some reason, yet he would like for the CI runners to be using VS2026, this makes the change official and moves the CI runner to VS2026 as well.
Rather than suppressing them, I fixed some warnings that show up when building with VS2026 too.