nethack-gwaa-kiwi/nethack
1
0
Fork 0
Code Pull Requests Activity

Windows instructions update

Browse Source
This commit is contained in:
nhmall
2018-04-21 09:33:47 -04:00
parent 56ceea5a41
commit a7df684d25
1 changed files with 19 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sys/winnt/Install.nt
+19 -12
View File
@@ -1,11 +1,11 @@
Copyright (c) NetHack Development Team 1990-2017 Copyright (c) NetHack Development Team 1990-2018
NetHack may be freely redistributed. See license for details. NetHack may be freely redistributed. See license for details.
============================================================== ==============================================================
Instructions for compiling and installing Instructions for compiling and installing
NetHack 3.6 on a Windows system NetHack 3.6 on a Windows system
(Windows 7/8.x/10 or later only. XP may work but is untested) (Windows 7/8.x/10 or later only. XP may work but is untested)
============================================================== ==============================================================
Last revision: $NHDT-Date: 1450306349 2015/12/16 22:52:29 $ Last revision: $NHDT-Date: 1524317622 2018/04/21 13:33:42 $
Credit for the porting of NetHack to the Win32 Console Subsystem goes to Credit for the porting of NetHack to the Win32 Console Subsystem goes to
the NT Porting Team started by Michael Allison. the NT Porting Team started by Michael Allison.
@@ -56,9 +56,13 @@ The Visual Studio 2017 NetHack solution file can be found here:
So the steps are: So the steps are:
1. Launch the IDE. 1. Launch the IDE.
2. Open the appropriate solution file. 2. Open the appropriate solution file.
3. Select the build configuration you wish to use. 3. If you have a newer version of Visual Studio than what was used to build
4. From build menu, select build solution. the solution and project files distributed with the NetHack sources, you
5. Type F5 to start debugging. can easily retarget the solution before the next step. Refer to the
"Note about the Windows SDK version" a couple of paragraphs below.
4. Select the build configuration you wish to use (Release, Debug, etc.).
5. From the build menu, select build solution.
6. Type F5 to start debugging.
You can also build all the projects for all platforms and configurations You can also build all the projects for all platforms and configurations
using a "build.bat" batch file found in the same directory as the solution. using a "build.bat" batch file found in the same directory as the solution.
@@ -66,10 +70,13 @@ using a "build.bat" batch file found in the same directory as the solution.
Change to the appropriate directory (i.e. win\win32\vs2015 for VS2015 builds, Change to the appropriate directory (i.e. win\win32\vs2015 for VS2015 builds,
win\win32\vs2017 for VS2017 builds) and run "build.bat". win\win32\vs2017 for VS2017 builds) and run "build.bat".
Note: The Visual Studio project files distributed for NetHack 3.6.1 are configured for the -----------------------------------
Windows SDK version 10.0.15063.0. At the time of writing, the Windows SDK version that Note about the WINDOWS SDK Version:
is distributed with VS2017 Community Edition is a newer 10.0.16299.0. If you have a build -----------------------------------
error MSB8036, you will simply need to change the expected SDK version as follows: The Visual Studio project files distributed for NetHack 3.6.1 are configured for the
Windows SDK version 10.0.15063.0. At the time of writing, the Windows SDK version that
is distributed with VS2017 Community Edition is a newer 10.0.16299.0. If you have a build
error MSB8036, you will simply need to change the expected SDK version as follows:
o Open the solution in the IDE and in the project property pages, right-click the o Open the solution in the IDE and in the project property pages, right-click the
solution and select "Retarget solution". solution and select "Retarget solution".
@@ -203,9 +210,9 @@ Setting Up
| | | | | |
share winnt win32 share winnt win32
Check the file "Files" in your top level directory for an exact Check the file "Files" in your top level directory for a more
listing of what file is in which directory. In order for the complete listing of what file is in which directory. In order for
Makefiles to work, all the source files must be in the proper the Makefiles to work, all the source files must be in the proper
locations. locations.
If you downloaded or ftp'd the sources from a UNIX system, the lines If you downloaded or ftp'd the sources from a UNIX system, the lines