Skip to content

Add support for MSVS 2026#26131

Closed
PBfordev wants to merge 1 commit intowxWidgets:masterfrom
PBfordev:msvs2026
Closed

Add support for MSVS 2026#26131
PBfordev wants to merge 1 commit intowxWidgets:masterfrom
PBfordev:msvs2026

Conversation

@PBfordev
Copy link
Copy Markdown
Contributor

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).

Update wx_config.props, add MSVS 2026 solutions for the library
and samples, and update the docs.
Comment thread docs/msw/install.md
(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.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

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.

@vadz
Copy link
Copy Markdown
Contributor

vadz commented Jan 29, 2026

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).

@vadz vadz closed this in 3d88038 Jan 29, 2026
@PBfordev
Copy link
Copy Markdown
Contributor Author

@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.

@vadz
Copy link
Copy Markdown
Contributor

vadz commented Jan 30, 2026

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!

@PBfordev
Copy link
Copy Markdown
Contributor Author

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?

@vadz
Copy link
Copy Markdown
Contributor

vadz commented Feb 6, 2026

See #26165 for the CI job.

@PBfordev Would it be possible to add the solution files for the tests (non-GUI and GUI ones) and wxrc too? TIA!

@PBfordev PBfordev deleted the msvs2026 branch February 10, 2026 06:26
RobertRoeb pushed a commit to RobertRoeb/wxWidgets that referenced this pull request Apr 7, 2026
Update wx_config.props, add MSVS 2026 solutions for the library
and samples, and update the docs.

Closes wxWidgets#26131.
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.

2 participants