VS does generate its own internal manifest file, but since we're using cmake now instead of proper VS projectfiles
we don't have the ability to just tick a box to enable HDPI support (or any other change we want). There are ways
to merge manifest files (mt.exe) which might be preferable to this, but I can't figure out how to use them.
From the impressive number of 9 start menu shortcuts, 2 were removed.
An additional 4 were removed for Windows 8, where the app list can't collapse folders.
The title is now localized, as are the start menu shortcuts. As localized
titles can be longer than the English string, a third line was explicitly
added to the welcome page (else NSIS cuts the line in half).
The manual shortcut points to the translated manual version, if available.
Due to lack of Unicode support in NSIS 2, only translations matching the
codepage are displayed correctly.
The desktop.ini file isn't removed during uninstallation as it may contain
info on other programs, e.g. if the player chose to place the shortcuts in
'Games'.
Fixed an issue caused by 659b9a4 - the 'Start Debugging' option was
basically useless as the process terminates itself if OMP_WAIT_POLICY
isn't defined.
Cleaned up unnecessary configurations for WindowsTimeout.
Fixed duplicate manifest.
Disabled WML unit tests on MSVC Debug builds as they would quintuple build
duration (over 60s per test).
Re-enabled stdout redirection in WML_tests.cmd to avoid spamming the
command line.
Updated vcproj for daa2140 (added multimenu widget).
For the numeric fields, this means we get to treat all X.Y.Z versions as
X.Y.Z.0, and there's no string suffix for those for obvious reasons. Not
that anyone cares, really.
Now we get a pretty name for our client process in the Task Manager too,
hooray!
(Also cleaned-up some of the placeholder code that was left here by
loonycyborg.)
This is needed so GetVersionEx doesn't lie to us on these versions.
MSVC++ people: I have no idea how this will interact with your building
procedure, if at all. In particular, I believe MSVC++ is supposed to
produce its own manifest declaring our dependencies on the MSVC++
runtime libraries, and it may or may not emit the compatibility
information as well.
It causes wesnoth to be run with installer's privileges which is
security concern and also might result in confusing behavior wrt
location of stdout.txt and stderr.txt files.
