Add support for MSVS 2026 (PR #26131)
PB
Update wx_config.props, add MSVS 2026 solutions for the library and samples, and update the docs.
I have tried to unify using MSVS (IDE) and MSVC (compiler) in the matching context.
I have also slightly changed wording when it comes to the CRT (to not mention the old msvcrt explicitly).
You can view, comment on, or merge this pull request online at:
https://github.com/wxWidgets/wxWidgets/pull/26131
Commit Summary
- 8ca3780 Add support for MSVS 2026
File Changes
(5 files)
- M README.md (2)
- M build/msw/wx_config.props (1)
- A build/msw/wx_vc18.slnx (87)
- M docs/msw/install.md (66)
- A samples/samples_vc18.slnx (1373)
Patch Links:
- https://github.com/wxWidgets/wxWidgets/pull/26131.patch
- https://github.com/wxWidgets/wxWidgets/pull/26131.diff
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
PB
@PBfordev commented on this pull request.
> - (VC++ only.) Set this variable to build for x86_64 systems. If unset, x86 - build is performed. + (MSVC only.) Set this variable to build for the target architecture. If unset, + the the default architecture for the active Developer Command Prompt is used.⬇️ Suggested change
- the the default architecture for the active Developer Command Prompt is used. + then the default architecture for the active Developer Command Prompt is used.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26131)Nice, thanks! I'll merge it soon and we should add CI builds using this compiler as soon as it becomes available (I'll subscribe to this issue and that one to be notified when it happens).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
PB
PBfordev left a comment (wxWidgets/wxWidgets#26131)@vadz, thanks for the quick merge.
I believe that at least the wx_config.props change should be backported, otherwise the solutions open with some ancient (and probably unavailable) toolset version sert and all projects need to be retargeted.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Thomas Krebs
wx_config_props.props would not be necessary.
Am 30.01.2026 um 05:11 schrieb PB:
> *PBfordev* left a comment (wxWidgets/wxWidgets#26131) <https://
> github.com/wxWidgets/wxWidgets/pull/26131#issuecomment-3822924800>
>
> @vadz <https://github.com/vadz>, thanks for the quick merge.
> I believe that at least the |wx_config.props| change should be
> backported, otherwise the solutions open with some ancient (and probably
> unavailable) toolset version sert and all projects need to be retargeted.
>
> —
> wxWidgets/wxWidgets/pull/26131#issuecomment-3822924800>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/
> AXD7XGHFWNDGPBRBV756TLL4JMU5JAVCNFSM6AAAAACTLST7I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRSHEZDIOBQGA>.
> You are receiving this because you are subscribed to this thread.Message
> ID: <wxWidgets/wxWidgets/pull/26131/c3822...@github.com>
>
> --
> You received this message because you are subscribed to the Google
> Groups "wx-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to wx-dev+un...@googlegroups.com <mailto:wx-
> dev+uns...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/wx-dev/
> wxWidgets/wxWidgets/pull/26131/c3822924800%40github.com <https://
> groups.google.com/d/msgid/wx-dev/wxWidgets/wxWidgets/pull/26131/
> c3822924800%40github.com?utm_medium=email&utm_source=footer>.
VZ
vadz left a comment (wxWidgets/wxWidgets#26131)I would be fine for backporting all/most of this PR, so if you have time to test it with 3.2 to confirm that it works there and open a PR against 3.2 branch, it would be great, TIA!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
PB
PBfordev left a comment (wxWidgets/wxWidgets#26131)Thomas Krebs wrote on wx-dev
You can set the toolset version to $(DefaultPlatformToolset), then the wx_config_props.props would not be necessary.
I wonder if we really (still) need to set all the stuff there, does MSBuild not select a reasonable default when it is not set?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.