IMO, it's easier and more future-proof to use CMake and generate a
solution and project files using CMake.
This continues to work with new editions of Visual Studio (providing
you have an appropriately updated CMake) without requiring any changes
from wxWidgets itself.
This is how I've been configuring/building wxWidgets from source for
years over many different updates of Visual Studio and never had a
problem. I create a CMakeUserPresets.json that looks like this:
...
"configurePresets": [
{ "name": "default",
"inherits": [ "with_samples", "with_tests", "vs2026" ]
},
{ "name": "vs2026",
"hidden": true,
"generator": "Visual Studio 18 2026"
}
]
(I have other personal preferences applied, but this is the relevant
bit for this conversation.)
then:
cmake --preset default
and presto, I have VS 2026 solution and project files. The
"with_samples" and "with_tests" configure presets ship with wxWidgets
itself and are defined in CMakePresets.json, which is the place for
shared presets. CMakeUserPresets.json is for your own personal
presets.
--
"The Direct3D Graphics Pipeline" free book <
http://tinyurl.com/d3d-pipeline>
The Terminals Wiki <
http://terminals-wiki.org>
The Computer Graphics Museum <
http://computergraphicsmuseum.org>
Legalize Adulthood! (my blog) <
http://legalizeadulthood.wordpress.com>