- 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.
When git is available, remove manual steps to maintain and update the
windows-build support even for cases where windows-build may have
previously extracted from a downloaded zip file.
Some git capable environments on Windows don't honor the installed git
hook scripts in the repository. Now that, if we're working within a git repo,
we force a working version of git to be installed in the runtime path. We
leverage that to force a validation of the commit id on each build.
- All projects use identical include directories, library definitions and
library directories.
- Remove attempts to add XP support to projects that were converted to
.vcxproj for post VC2008 versions of Visual Studio.
- Require that git be available when building within a git repository
working directory.
When the git hooks have changed and git isn't in the path, the correct git
commit id can't be determined and thus be available to be included in
the build. This change announces that fact and stops a build.
This only happens if git is installed locally and available in the current
path when Visual Studio executes. Whether git is in the path is an
installation option when git for Windows is installed.
Otherwise, proper results should be available after subsequent
activity on the local repository. Any build will install the git hooks
that properly populate .git-commit-id when any changes are made
to the local repo.
The BuildROMs project now runs the BuildROMs program that was most
recently built (Debug or Release). This will identify ROM data inconsistencies
that may exist at build time.
When building other projects which may depend on ROM data, the BuildROMs
is run as a sanity check and if it fails we make sure that we hadn't run an out
of date Release build version of the BuildROMs binary.
The project migration process from VS2008 to VS2015 doesn't bring in
project/solution wide migration compile defines that are introduced in
Visual Studio Community's migration which adds _USING_V110_SDK71.
This affects source modules which explicitly don't inherit project wide
defines. The compile of pthread.c (in various projects) is such a case.
