Skip to content

Conversation

@Repiteo
Copy link
Contributor

@Repiteo Repiteo commented Nov 13, 2025

Implements baseline support for the recently released Visual Studio 2026. More advanced additions like .slnx detection/construction are not required for VS2026 to function; consequently, they're outside the scope of this PR.

Contributor Checklist:

  • I have created a new test or updated the unit tests to cover the new/changed functionality.
  • I have updated CHANGES.txt and RELEASE.txt (and read the README.rst).
  • I have updated the appropriate documentation

@mwichmann mwichmann added the MSVC Microsoft Visual C++ Support label Nov 13, 2025
@mwichmann mwichmann added this to 4.10.1 Nov 13, 2025
@mwichmann mwichmann added this to the NextRelease milestone Nov 13, 2025
@mwichmann
Copy link
Collaborator

Thanks for this! @bdbaddog was going to look at it over the weekend, now all he has to do is review :-)

@mwichmann
Copy link
Collaborator

We'll want to integrate this into CI, but at the moment support is not available. We can track actions/runner-images#13291 and make a separate PR for that topic.

@mwichmann mwichmann moved this to In progress in 4.10.1 Nov 13, 2025
@bdbaddog bdbaddog merged commit 3b4bdfa into SCons:master Nov 13, 2025
10 of 11 checks passed
@github-project-automation github-project-automation bot moved this from In progress to Done in 4.10.1 Nov 13, 2025
@bdbaddog
Copy link
Contributor

Thanks for the PR!

@Repiteo Repiteo deleted the VS2026 branch November 13, 2025 20:39
@Delsin-Yu
Copy link

Delsin-Yu commented Nov 14, 2025

Details image

For some reason, it looks like SCons is still unable to detect the CL from Visual Studio 2026 with this PR.

Never mind, I reinstalled VS2026 and it works again. I guess me desperatly switching between VS, VS-Build-Tools, and MSVC versions eventually destroyed my Visual Studio environment variables yesterday.

@mwichmann
Copy link
Collaborator

Never mind, I reinstalled VS2026 and it works again. I guess me desperatly switching between VS, VS-Build-Tools, and MSVC versions eventually destroyed my Visual Studio environment variables yesterday.

eh, that's been known to happen (to me, at least). Glad it's working - let us know (probably open an issue, since this is marked completed) if there are other problems.

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

Labels

MSVC Microsoft Visual C++ Support

Projects

No open projects
Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants