Add support for Visual Studio 2026#2509
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughAdded 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
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
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. |
|
Hi. Sorry, is there any documentation on building ACE and TAO? I can't find it. |
|
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. |
|
Depends on DOCGroup/MPC#242 |
|
Okay, Seems good. |
| feature(ace_languagestandard2017) { | ||
| specific(vs2017,vs2019,vs2022) { | ||
| specific(vs2017,vs2019,vs2022,vs2026) { | ||
| LanguageStandard = stdcpp17 |
There was a problem hiding this comment.
Don't think vs2026 needs this overwritten standard version
There was a problem hiding this comment.
CI tests in DOCGroup/MPC#242 failed because this option was missing. Will merging the PR with this option removed solve the problem?
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
think this feature is not necessary
Summary by CodeRabbit
New Features
Chores
Documentation