Skip to content

Update to VS26#419

Merged
Detanup01 merged 21 commits into
devfrom
vs-26-and-clang
May 15, 2026
Merged

Update to VS26#419
Detanup01 merged 21 commits into
devfrom
vs-26-and-clang

Conversation

@Detanup01
Copy link
Copy Markdown
Owner

Completes #387

@Detanup01
Copy link
Copy Markdown
Owner Author

Sadly no idea how to propertly download the right version for the 3rd party ones

@Detanup01
Copy link
Copy Markdown
Owner Author

man VSC is horrible with managing submodules

@Detanup01 Detanup01 changed the title update 3rdparty and win premake buildscript Update to VS26 Jan 27, 2026
@Detanup01 Detanup01 marked this pull request as draft January 27, 2026 18:44
@Detanup01
Copy link
Copy Markdown
Owner Author

This sucks.
VS26 isnt in github actions.
I gonna kms

@Detanup01
Copy link
Copy Markdown
Owner Author

Ignore linux since those need newer ones which this one might not have

@Detanup01
Copy link
Copy Markdown
Owner Author

I left this here:

git submodule set-branch --branch thirdparty-deps-update third-party/deps/common
git submodule set-branch --branch thirdparty-common-linux-premake third-party/common/linux
git submodule set-branch --branch thirdparty-common-win-premake third-party/common/win
git submodule update --remote third-party/deps/common
git submodule update --remote third-party/common/linux
git submodule update --remote third-party/common/win

@Detanup01 Detanup01 marked this pull request as ready for review May 4, 2026 18:58
@Detanup01
Copy link
Copy Markdown
Owner Author

dry run rn not works on linux will see tmr

@Detanup01
Copy link
Copy Markdown
Owner Author

Everything works now

@Detanup01 Detanup01 requested review from universal963 and removed request for universal963 May 5, 2026 14:26
@Detanup01 Detanup01 self-assigned this May 5, 2026
@Detanup01
Copy link
Copy Markdown
Owner Author

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

May 15-ish will be the update

@Detanup01 Detanup01 merged commit ea1fe61 into dev May 15, 2026
68 checks passed
@Detanup01 Detanup01 deleted the vs-26-and-clang branch May 15, 2026 15:16
@Mitch037
Copy link
Copy Markdown

This commit broke compatibility with Windows 7, 8 and 8.1. VS26 minimum requirement is Windows 10.
The issue-related thread on the official VS26 forums.
Would it be possible to create a branch of gbe_fork built with VS22 which is compatible with older Windows versions?

@universal963
Copy link
Copy Markdown
Collaborator

Indeed, as what I have said in #387, "a breaking change notice is strongly recommended."

@Detanup01
Copy link
Copy Markdown
Owner Author

Isnt this only for building?
iirc premake update also required to update from old linux (ub20 => ub22)

Can try 2 builds but linux one dont think can be backward to ub20 so.
iirc you can just replace specific windows build stuff to build as vs22 instead (windows-2022)

@Detanup01
Copy link
Copy Markdown
Owner Author

Its easy to add back support to build with vs22 since it just a few edit and copy-paste.
But cant do much for linux unfortunately

@Mitch037
Copy link
Copy Markdown

Isnt this only for building?

It's not just about building, it's about using gbe_fork. The latest version of gbe_fork (2026/05/16) requires Windows 10/11 to run. I mean gbe_fork doesn't work if you try to launch games on Win7/8/8.1. It throws GetSystemTimePreciseAsFileTime() not found in Kernel32.dll error.

@Detanup01
Copy link
Copy Markdown
Owner Author

#515 This adds back VS22

@God-damnit-all
Copy link
Copy Markdown

God-damnit-all commented May 18, 2026

For posterity (because things on Microsoft sites have a tendency to vanish due to their inability to stop touching things):

💬︎ Stephan T. Lavavej [MSFT]
This was my change and the behavior is by design. For efficiency on modern OSes, we’re unconditionally using new APIs, which is what produces the error you’re seeing. We don’t have an easy way to emit a graceful message on Win7, and we don’t have the capacity to spend additional engineering effort on this. However, I did update the VCRedist installer so it will fail with a clear message when installed on Win7 or Win8.0. (For technical reasons we can’t distinguish Win8.1, but that scenario is still unsupported; Win10 is the minimum requirement.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants