solemnwarning/wxwidgets
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 4

Prune mentions of no longer supported compilers from the docs

Browse source 
Remove mentions of older MSVC versions and very old gcc versions.
This commit is contained in:
PB 2022-10-11 18:15:58 +02:00 • committed by Vadim Zeitlin
parent 7ae3cf206c
commit a2b84d40a0
5 changed files with 28 additions and 47 deletions
Download patch file Download diff file Expand all files Collapse all files

33
docs/msw/install.md
View file

@ -49,11 +49,9 @@ Microsoft Visual C++ Compilation {#msw_build_msvs}
### From the IDE
Ready to use project files are provided for VC++ versions 8, 9,
10, 11, 12, 14, 15, 16 and 17 (also known as MSVS 2005, 2008, 2010, 2012,
2013, 2015, 2017, 2019 and 2022 respectively).
Ready to use project files are provided for VC++ versions 2015, 2017, 2019 and 2022.
Simply open `wx_vcN.sln` (for N=8, 9, 10, 11, 12, 14, 15, 16 or 17) file,
Simply open `wx_vcN.sln` (for N=14, 15, 16 or 17) file,
select the appropriate configuration (Debug or Release, static or DLL)
and build the solution. Notice that when building a DLL configuration,
you may need to perform the build several times because the projects
@ -116,9 +114,9 @@ contributors. If the version is out of date, please [create an issue or pull req
### Special notes for Visual Studio 2010+
### Special notes for Visual Studio
For Visual Studio 2010+ solutions it is possible to customize the build by
For Visual Studio solutions it is possible to customize the build by
creating a `wx_local.props` file in the `build\msw` directory which is used, if it
exists, by the projects. The settings in that file override the default values
for the properties such as wxCfg (corresponding to the CFG makefile variable
@ -131,8 +129,8 @@ of Visual Studio you could change wxCompilerPrefix to include the toolset:
- <wxCompilerPrefix>vc</wxCompilerPrefix>
+ <wxCompilerPrefix>vc$(PlatformToolsetVersion)</wxCompilerPrefix>
Following that example if you are using Visual Studio 2013 and open
`wx_vc12.sln` it will build using the "vc120" prefix for the build directories
Following that example if you are using Visual Studio 2015 and open
`wx_vc14.sln` it will build using the "vc140" prefix for the build directories
so to allow its build files to coexist with the files produced by the other
MSVC versions.
@ -143,16 +141,13 @@ updated with it. For example the version information in `wx_setup.props` could
change and the information in your `wx_local.props` would be outdated. It is
your responsibility to monitor for such situations.
### Improve debugging for Visual Studio 2012+
### Improve debugging for Visual Studio
Debug visualizers for Visual Studio 2012+ are provided which makes inspecting
various wxWidgets classes easier to view while debugging. To use them:
1. Open the folder `%%WXWIN%\misc\msvc`
2. Open the folder `%%USERPROFILE%\My Documents\Visual Studio 2012\Visualizers`
(or the corresponding location for newer versions, e.g. `...2013\Visualizers`)
3. Copy `wxWidgets.natvis` and `autoexp.inc`
4. For Visual Studio 2013+ additionally copy `wxWidgets.2013.natvis`
Debug visualizers which make inspecting various wxWidgets classes easier to view
while debugging are provided in file `%%WXWIN%\misc\msvc\wxWidgets.natvis`.
The visualisers can be either added to a project or installed system-wide.
See the [Visual Studio documentation](https://learn.microsoft.com/en-us/visualstudio/debugger/create-custom-views-of-native-objects)
for more information.
MinGW Compilation {#msw_build_mingw}
@ -473,8 +468,6 @@ Here is what you need to do:
- `_UNICODE` unless you want to use deprecated ANSI build of wxWidgets.
- `NDEBUG` if you want to build in release mode, i.e. disable asserts.
- `WXUSINGDLL` if you are using DLL build of wxWidgets.
* If using MSVC 7 only (i.e. not for later versions), also define
`wxUSE_RC_MANIFEST=1` and `WX_CPU_X86`.
* Add `<wx-lib-dir>` directory described above to the libraries path.
When using MSVC, the libraries are linked automatically using "#pragma
@ -497,7 +490,7 @@ instructions here are out of date, you can always simply copy a makefile or
project file from `$WXWIN\samples\minimal` or some other sample and adapt it to
your application.
If you are not using Visual Studio 2010 or newer please see
If you are not using Visual Studio please see
@subpage plat_msw_winxp "Windows XP Support" to enable visual styles in your
application.