Skip to content

Add support for Visual Studio 2026#2509

Open
hwangsihu wants to merge 3 commits intoDOCGroup:masterfrom
hwangsihu:master
Open

Add support for Visual Studio 2026#2509
hwangsihu wants to merge 3 commits intoDOCGroup:masterfrom
hwangsihu:master

Conversation

@hwangsihu
Copy link

@hwangsihu hwangsihu commented Mar 4, 2026

Summary by CodeRabbit

  • New Features

    • Added support for Visual Studio 2026, including updated compiler/toolset and project templates for VS2026.
  • Chores

    • Updated CI workflows to include Windows builds using Visual Studio 2026.
  • Documentation

    • Added a NEWS entry announcing Visual Studio 2026 support.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 4, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 18f06677-5807-4668-8f2a-ebf97a1c83da

📥 Commits

Reviewing files that changed from the base of the PR and between fcf88ad and a0b4738.

📒 Files selected for processing (1)
  • .github/workflows/windows.yml

Walkthrough

Added Visual Studio 2026 support: CI workflow matrix entries, a new MSVC 14.5 config header, updated MSVC version gating, VS2026 build feature and nmake config files, and a NEWS entry documenting the addition.

Changes

Cohort / File(s) Summary
CI Workflows
\.github/workflows/cmake.yml, \.github/workflows/windows.yml
Added VS2026 matrix entries targeting windows-2025-vs2026 runner with vs2026 toolset and x64 Debug/Release variants; mirrors existing VS entries.
MSVC Configuration
ACE/ace/config-win32-msvc-145.h, ACE/ace/config-win32-msvc.h
Added new MSVC 14.5 config header defining ACE_WIN32_VC145; updated _MSC_VER gating in config-win32-msvc.h to include the new header when _MSC_VER >= 1950.
Build System Configuration
ACE/bin/MakeProjectCreator/config/vs2026.features, ACE/bin/MakeProjectCreator/config/vs2026nmake.mpb
New VS2026 feature file (ssl=0, qos=1, rwho=0, sctp=0) and nmake config disabling /Wp64 and /Gm and suppressing VC warnings 4456/4458/4459 for nmake backend.
Documentation
ACE/NEWS
Added an entry noting Visual Studio 2026 support.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Poem

🐰 Hop! VS2026 hops into sight,
New configs snug, compiled just right.
Workflows hum and feature files sing,
Nmake trims flags—what joy they bring!
ACE and I nibble code with delight.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add support for Visual Studio 2026' clearly and directly summarizes the main change across all modified files, which consistently add VS 2026 configuration support.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@jwillemsen
Copy link
Member

Have you done a full build with tests? On github CI we only compile a small part of the code and don't run tests at all.

@hwangsihu
Copy link
Author

Hi.

Sorry, is there any documentation on building ACE and TAO? I can't find it.

@jwillemsen
Copy link
Member

See https://htmlpreview.github.io/?https://github.com/DOCGroup/ACE_TAO/blob/master/ACE/ACE-INSTALL.html, at the bottom there are some instructions to build from git. Without a full build/test I think it is too early to say Visual Studio 2026 is supported, maybe it compiles the core, but the real test is a full build/test and also look at warnings and runtime test results.

@hwangsihu hwangsihu marked this pull request as draft March 4, 2026 10:37
@jwillemsen
Copy link
Member

Depends on DOCGroup/MPC#242

@hwangsihu
Copy link
Author

Okay, Seems good.

@hwangsihu hwangsihu marked this pull request as ready for review March 4, 2026 15:24
feature(ace_languagestandard2017) {
specific(vs2017,vs2019,vs2022) {
specific(vs2017,vs2019,vs2022,vs2026) {
LanguageStandard = stdcpp17
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think vs2026 needs this overwritten standard version

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI tests in DOCGroup/MPC#242 failed because this option was missing. Will merging the PR with this option removed solve the problem?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default C++ version for Visual Studio 2026 is C++20 as far as I can determine from public documentation, so something to investigate and test more.


feature(ace_languagestandard2017) {
specific(nmake) {
compile_flags += /std:c++17
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

think this feature is not necessary

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants