The I650 simulator depends on the sim_card library which had API chages that
the author agreed to before the changes were committed, but no update of the
I650 simulator code has come for the past 2 months.
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.
- New Commit-Id with Commit-Time
- Properly execute when the Win32-Development-Binaries needs to be cloned
- Properly limit parallel builds if the local system has more than 8 Threads
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.
These include simulators for the IBM 701, IBM 702, IBM 704, IBM 705,
IBM 705/3, IBM 709, IBM 1410/IBM 7010, IBM 7070, IBM 7080, IBM 7090
and IBM7094.
These basically were a collection of machines that shared a common
set it peripherals, Each group had its own instruction set, hence
different simulators.
IBM 701 -> i701
IBM 702/705/705/3/7080 -> i7080
IBM 7070/7074 -> i7070
IBM 1410/7010 -> i7010
IBM 704 -> i704
IBM 704/709/7090/7094 -> i7090
The i7090 can be set to simulate a IBM 704 however you end up
disabling almost everything, since the 704 did not have any channels.
A build option exists that allows this one to be built without all the
extra features.
The i7090 simulator’s implementation of the IBM 7094 is a more
complete implementation of the IBM 7094 which can run CTSS
while the existing simh I7094 can’t.
