mirror of
https://github.com/simh/simh.git
synced 2026-01-13 23:35:57 +00:00
f98a4ca93a
- 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.
116 lines
5.6 KiB
Plaintext
116 lines
5.6 KiB
Plaintext
This dirctory contains a set of Visual Studio 2008 build projects for the
|
|
current simh code base. When used (with Visual Studio Express 2008 or
|
|
or a later Visual Studio version) it populates a directory tree under the
|
|
BIN directory of the Simh distribution for temporary build files and
|
|
produces resulting executables in the BIN/NT/Win32-Debug or
|
|
BIN/NT/Win32-Release directories (depending on whether you target a Debug
|
|
or Release build).
|
|
|
|
These projects, when used with Visual Studio 2008, will produce Release
|
|
build binaries that will run on Windows versions from XP onward. Building
|
|
with later versions of Visual Studio will have different Windows version
|
|
compatibility.
|
|
|
|
The Visual Studio Projects expect that various dependent packages that
|
|
the simh code depends on are available in a directory parallel to the
|
|
simh directory.
|
|
|
|
For Example, the directory structure should look like:
|
|
|
|
.../simh/sim-master/VAX/vax_cpu.c
|
|
.../simh/sim-master/scp.c
|
|
.../simh/sim-master/Visual Studio Projects/simh.sln
|
|
.../simh/sim-master/Visual Studio Projects/VAX.vcproj
|
|
.../simh/sim-master/BIN/Nt/Win32-Release/vax.exe
|
|
.../simh/windows-build/pthreads/pthread.h
|
|
.../simh/windows-build/winpcap/WpdPack/Include/pcap.h
|
|
.../simh/windows-build/libSDL/SDL2-2.0.3/include/SDL.h
|
|
|
|
If you have a command line version of git installed in your environment
|
|
then the windows-build repository will be downloaded and updated
|
|
automatically. Git for windows can be downloaded from:
|
|
|
|
https://git-scm.com/download/win
|
|
|
|
If git isn't available, and you're running on a recent version of
|
|
Windows (10 or 11), then the contents of the windows-build
|
|
directory will be automatically downloaded and installed in the
|
|
appropriate location relative to the simh source.
|
|
|
|
Network devices are capable of using pthreads to enhance their performance.
|
|
To realize these benefits, you must build the desire simulator with
|
|
USE_READER_THREAD defined. The relevant simulators which have network
|
|
support are all of the VAX simulators, the PDP11 simulator and the various
|
|
PDP10 simulators.
|
|
|
|
Additionally, simulators which contain devices that use the asynchronous
|
|
APIs in sim_disk.c and sim_tape.c can also achieve greater performance by
|
|
leveraging pthreads to perform blocking I/O in separate threads. Currently
|
|
the simulators which have such devices are all of the VAX simulators and
|
|
the PDP11. To achieve these benefits the simulators must be built with
|
|
SIM_ASYNCH_IO defined.
|
|
|
|
The project files in this directory build these simulators with support for
|
|
both network and asynchronous I/O.
|
|
|
|
To build any of the supported simulators you should open the simh.sln file
|
|
in this directory.
|
|
|
|
The installer for Visual Studio 2008 SP1 is available from:
|
|
|
|
https://download.microsoft.com/download/E/8/E/E8EEB394-7F42-4963-A2D8-29559B738298/VS2008ExpressWithSP1ENUX1504728.iso
|
|
|
|
Then install Visual Studio Express Visual C++ by executing VCExpress\setup.exe
|
|
on that DVD image. No need to install "Silverlight Runtime" or
|
|
"Microsoft SQL Server 2008 Express Edition". Depending on your OS Version
|
|
you may be prompted to install an older version of .NET Framework which should
|
|
be installed.
|
|
|
|
Visual Studio Express 2008 will build executables that will run on all Windows
|
|
versions from XP onward with equivalent functionality.
|
|
|
|
Note: VS2008 can readily coexist on Windows systems that also have later
|
|
versions of Visual Studio installed.
|
|
|
|
If you are using a version of Visual Studio beyond Visual Studio 2008, then
|
|
your later version of Visual Studio will automatically convert the Visual
|
|
Studio 2008 project files. You should ignore any warnings produced by the
|
|
conversion process.
|
|
|
|
If you have a version of Visual Studio installed and want to build all the
|
|
simulators from a command prompt, the file build_vstudio.bat in the root
|
|
of the simh source tree will do that without any furthur interaction.
|
|
|
|
Almost all newer Visual Studio versions after VS2008 will build executables
|
|
that only run on the system that built it or one running the same OS.
|
|
|
|
If you're using Visual Studio Community 2022, and you follow these
|
|
installation instructions, you can also build simulator executables which
|
|
will run on all versions of Windows from XP onward if you install as
|
|
indicated here and you use the build_vstudio.bat file to perform the
|
|
project conversions. Once projects are converted, they can be used in
|
|
the Visual Studio 2022 IDE for further development.
|
|
|
|
- New install
|
|
- In the "Workloads" pane, check "Desktop development with C++" workload's
|
|
checkbox, if not already checked.
|
|
- Click on the tab labeled "Individual components"
|
|
- In the "Individual components" pane:
|
|
- Enter "XP" in the "Search components (Ctrl-Q)" field.
|
|
- Locate the "Compilers, build tools and runtimes" heading
|
|
- Select "C++ for Windows XP Support for VS 2017 (v141) tools [Deprecated]" checkbox.
|
|
- Continue to customize your VS 2022 installation as needed.
|
|
- Click on "Install" in the lower right hand corner
|
|
|
|
- Modifying an existing VS2022 installation
|
|
- Click on the Visual Studio 2022 `Modify` button.
|
|
- In the "Modifying --" window, click on "Individual Components"
|
|
- Click on the tab labeled "Individual components"
|
|
- In the "Individual components" pane:
|
|
- Enter "XP" in the "Search components (Ctrl-Q)" field.
|
|
- Locate the "Compilers, build tools and runtimes" heading
|
|
- Select "C++ for Windows XP Support for VS 2017 (v141) tools [Deprecated]" checkbox.
|
|
- Continue to customize your VS 2022 installation as needed.
|
|
- Click on the "Modify" button in the lower right corner of the Window.
|
|
|