- Cleanup build details and provide initial detection support for
building Visual Studio 2026.
- Automatically leverage the v141 Visual Studio platform Toolset if
it is installed. This avoids failing build attempts when windows_build
hasn't yet been updated to support the frequently changing VS2022
or VS2026 build components.
- Fix pdp11.vcproj to avoid warning when project is converted.
- Fix trivial compiler warnings in alpha_cpu.c and hp_tapelib.c
build_vstudio.bat converts the .vcproj files from Visual Studio 2008 to
.vcxproj when used with newer versions of Visual Studio and configures
it to build XP-compatible binaries using the v141_xp toolset. However,
this toolset is deprecated and may not be present when using Visual
Studio 2022. The script intends to edit the .vcxproj files only in the
case where it exists; however, due to a logic error it actually does
this unconditionally. This causes the build to fail on VS2022 when
the XP toolset is not present.
When converting to a newer Visual Studio version, a new solution file is
created named simh-'vsversion'.sln so that we don't modify any files
managed by git. The resulting converted solution file will be automatically
used when build_vstudio.bat is subsequently run and that solution can be
opened directly by the Visual Studio IDE.
- Pre-Pre-Build-Event.cmd now dynamically determines the available
compiler version along with any alternate toolset which may be part
of the build environment and makes the appropriate windows-build
library support available for linking.
- build_vstudio.bat now supports VS2022 and will dynamically adjust
the converted VS2008 project files to leverage any available XP build
support which might be installed so that the generated executables
will support all versions of Windows from XP onward. The VS2008
generated executables automatically support all versions of Windows
from XP onward.
Similar to the build_ming.bat procedure which will invoke MinGW to
biuild siimulators, this procedure will rebuild all of SIMH simulators using
Visual Studio.
If this procedure is not invoked from a Developer Command Prompt
then the VS2008 tools are preferred if VS2008 is installed,
otherwise the installed Visual Studio tools will be used
prefering newer Visual Studio versions over older ones.
If this procedure is invoked from a Developer Command Prompt
then the tool chain provided with the command prompt is used
to build the simh projects.
A single argument to this procedure may be the word Debug, which
will cause Debug binaries to be build rather than the Release
binaries which is the default.
