splash.uu tiles-mingw32.mak tiles.mak
winMS.h
-win/win32/vs2017:
-(files for Visual Studio 2017 Community Edition builds)
+win/win32/vs:
+(files for Visual Studio 2017 or 2019 Community Edition builds)
NetHack.sln NetHack.vcxproj
NetHackPackage.appxmanifest NetHackPackage.wapproj
NetHackProperties.props NetHackW.vcxproj
tilemap.vcxproj tiles.vcxproj
travisci.sh uudecode.vcxproj
-win/win32/vs2017/Images:
+win/win32/vs/Images:
(files for Visual Studio 2017 Community Edition builds)
BadgeLogo.scale-100.png
BadgeLogo.scale-125.png
| | | | | |
share winnt tty win32 Lua-5.4.0 pdcurses
|
- vs2017
+ vs
/--------------------------------------------------------\
-| Building And Running Using Visual Studio 2017 |
+| Building And Running Using Visual Studio 2017 or 2019 |
\--------------------------------------------------------/
Before proceeding, please obtain the lua-5.4.0 sources and copy them to
https://github.com/lua/lua.git using the tag 'v5.4.0'. The build expects
to find lua files such as 'lua.h' at 'lib\lua-5.4.0\src\lua.h'.
-If you are NOT using Visual Studio 2017 IDE, or you prefer to build
+If you are NOT using Visual Studio 2017 or 2019 IDE, or you prefer to build
using a Make utility and a Makefile proceed to "Building Using Make".
-When using either Visual Studio 2017, you simply need to load the
+When using either Visual Studio 2017 or 2019, you simply need to load the
solution file within the IDE, build the solution and run the version
of NetHack you wish to run.
-The Visual Studio 2017 NetHack solution file can be found here:
- win\win32\vs2017\NetHack.sln
-
-You can use that same win\win32\vs2017\NetHack.sln with Visual Studio 2019,
-but you may have to retarget the projects:
- Windows SDK Version: 10.0.17763.0 [ There have been some reports of
- difficulties if you instead choose
- "10.0 (latest installed version)" ]
- Platform Toolset: Upgrade to v142
-
+The Visual Studio NetHack solution file can be found here:
+ win\win32\vs\NetHack.sln
Before executing the steps to build listed in the next paragraph,
decide if you want to include optional curses window-port. See
using a "build.bat" batch file found in the same directory as the solution.
Open a developer command prompt for the version of Visual Studio you are
-using. Change to the directory win\win32\vs2017 and run "build.bat".
+using. Change to the directory win\win32\vs and run "build.bat".
* Optional curses window-port support *
<ConfigurationType>Application</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
<CharacterSet>MultiByte</CharacterSet>
- <PlatformToolset>v141</PlatformToolset>
+ <PlatformToolset>$(DefaultPlatformToolset)</PlatformToolset>
<LocalDebuggerWorkingDirectory>$(BinDir)</LocalDebuggerWorkingDirectory>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)'=='Debug'" >
<UseDebugLibraries>false</UseDebugLibraries>
<WholeProgramOptimization>true</WholeProgramOptimization>
</PropertyGroup>
-
</Project>
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
<CharacterSet>MultiByte</CharacterSet>
- <PlatformToolset>v141</PlatformToolset>
+ <PlatformToolset>$(DefaultPlatformToolset)</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)'=='Debug'" >
<UseDebugLibraries>true</UseDebugLibraries>
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
<CharacterSet>MultiByte</CharacterSet>
- <PlatformToolset>v141</PlatformToolset>
+ <PlatformToolset>$(DefaultPlatformToolset)</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)'=='Debug'" >
<UseDebugLibraries>true</UseDebugLibraries>