State upfront that it only works with MSVC and also don't mention
msvcrt.dll not used any more since a couple of decades.

See #23715.

In the note about building wxWidgets with MinGW makefile and using
parallel build, explain that "-jN" option cannot be used when building
"setup_h" target.

Closes #23642.

The latter option will remain, while the former one won't be used at all
any longer soon, so prefer using the latter whenever possible.

This is important enough to be described directly there, especially now
when a manifest is required.

Don't make "Make Parameters" and "Advanced Configurations" top level
sections, they're not as important as the other ones.

Supporting XP requires too many hacks, and while it wouldn't be very
difficult to support Vista as long as we support Windows 7, it's still
not worth it because nobody uses this system anyhow.

Remove most of XP-specific code and don't use wxDynamicLibrary for using
the functions not present in it any longer.

Don't use <wspiapi.h> neither as we shouldn't use it any more.

Update some comments to not mention Windows versions not supported any
longer and also remove mentions of "Vista and newer Windows versions"
from the documentation as this is now always the case.

This commit is best viewed ignoring whitespace-only changes.

Just change "Windows XP" support to "Theme Support" when referring
to visual styles.

Also hardcode "u" suffix for the library names -- it doesn't make sense
any longer, but we need to keep it for compatibility.

It is now always defined, so testing for it is useless.

Give an error in MSVC-specific header if it is not defined as it should
be.

Remove mentions of older MSVC versions and very old gcc versions.

Update (hopefully all) the other enumerations of MSW versions to include
Windows 11 too.

Otherwise Doxygen interprets each path component as its command and
complains about "unknown \msw command" in "build\msw" path, for example.

Vcpkg defaults to installing packages for x86-windows, and from the
perspective of x64 builds, the packages installed just cannot be
found -- and the reason is not very obvious.

Having an example with commands that will install both x86 and x64 is
probably the right thing to do in this day and age -- and if somebody
only wants one and not the other, seeing a package name with architecture
specified helps with guessing how to achieve that.

Closes #22075.

Closes https://github.com/wxWidgets/wxWidgets/pull/2625

Te changes of 74c51eaf (Fix formatting of wxMSW build instructions,
2021-07-13) broke the rendered output of "%WXWIN%", for some reason the
leading percent sign needs to be double to appear correctly inside the
backticks, so do it to fix this.

Closes #19260.

Note that this support is still incomplete, notably we don't have
*_vc17.sln files yet and the official build scripts haven't been updated
to build MSVS 2022 binaries neither.

Closes https://github.com/wxWidgets/wxWidgets/pull/2477

Don't mention Cygwin any more, except as a build environment.

Do mention MSYS2 and WSL.

Also rename it to "Make Parameters" to make it more clear that it only
applies when using make.

It seems more logical to have it here rather than in its own top-level
section.

Use `%WXWIN%` instead of \%WXWIN\% and other similar fixes.

This shouldn't be true any longer, i.e. wxWidgets should (and does)
build with just -std=c++NN.

Using numbered lists with multiline items doesn't work in Markdown, so
remove it.

Also put the "IDE" part of the instructions before the "command line"
one, as it is probably use much more commonly.

No real changes to contents.

Simplify things by putting setup.h files themselves under version
control and getting rid of setup0.h ones.

The initial motivation for using separate setup0.h files was to allow
having local changes to setup.h, but with Git there is a simple way to
do it by using "git update-index --skip-worktree include/wx/msw/setup.h"
for example, so we don't really need setup0.h any more and dropping them
makes things simpler.

Run the same codespell command on docs directory.

Also describe a manual change which needs to be done at the project
level when creating a new empty project in MSVS.

Make command line instructions for vcpgk more similar to those used
for example for nmake. The MS Windows command line does not use $ as
the command prompt and batch files are more commonly used then Unix
shell scripts.

Closes https://github.com/wxWidgets/wxWidgets/pull/1785

Closes https://github.com/wxWidgets/wxWidgets/pull/1777

This file doesn't need to be created initially, as it will be done
automatically during the build, but it does need to be updated whenever
setup0.h changes, so explain this in both the README-GIT.md file and the
main build instructions.

Closes #18699.

Add directions for building wxQT/Win32 port under
MSys2 using configure/make.

The binaries-related files haven't been updated yet because we don't
provide 2019 binaries yet (build/tools/msvs/officialbuild.bat still has
to be updated too).

No real changes, just use backticks more consistently and extensively.

This replaces and extends the previous commit by using `$var` instead of
`$(var)` when this makes sense and using the ugly workaround for Doxygen
expanding environment variables even inside Markdown backticks elsewhere.

Also use backticks around more strings.

This seems to be the simplest possible way to let a MSVS project use the
library.