Install.nt updates
- Additional information for using MS VC++ 2005 Express Edition in combination with the Platform SDK.
This commit is contained in:
+90
-51
@@ -1,4 +1,4 @@
|
|||||||
Copyright (c) NetHack Development Team 1990-2005
|
Copyright (c) NetHack Development Team 1990-2006
|
||||||
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
|
||||||
@@ -21,9 +21,9 @@ You can build either the TTY version of NetHack or the Windows Graphical
|
|||||||
version. In either case you can use one of the following build
|
version. In either case you can use one of the following build
|
||||||
environments:
|
environments:
|
||||||
|
|
||||||
o A copy of Microsoft Visual C V6.0 SP3 or later. Things may work with
|
o A copy of Microsoft Visual C V6.0 SP3 or later, which includes
|
||||||
an earlier version of the compiler, but the current code has not
|
Visual C++ 2005 Express Edition plus the MS Platform SDK.
|
||||||
been tested with an earlier version.
|
The current code has not been tested with earlier versions.
|
||||||
|
|
||||||
OR
|
OR
|
||||||
|
|
||||||
@@ -34,10 +34,10 @@ environments:
|
|||||||
|
|
||||||
OR
|
OR
|
||||||
|
|
||||||
o A copy of MinGW 2.0. MinGW is a collection of header files and import
|
o A copy of MinGW 2.0 or later. MinGW is a collection of header
|
||||||
libraries with which native Windows32 programs can be made; the
|
files and import libraries with which native Windows32 programs
|
||||||
MinGW 2.0 distribution contains the GNU Compiler Collection.
|
can be built; the MinGW 2.0 distribution contains the GNU Compiler
|
||||||
You can download MinGW at
|
Collection. You can download MinGW at
|
||||||
http://www.mingw.org/
|
http://www.mingw.org/
|
||||||
Earlier versions of MinGW will not allow you to build the Windows
|
Earlier versions of MinGW will not allow you to build the Windows
|
||||||
Graphical version.
|
Graphical version.
|
||||||
@@ -48,10 +48,12 @@ that allow you to build the Windows Graphical version from Microsoft
|
|||||||
Visual C's IDE (Integrated Development Environment.)
|
Visual C's IDE (Integrated Development Environment.)
|
||||||
|
|
||||||
|
|
||||||
FIRST STEP
|
/-----------------------------------\
|
||||||
|
| FIRST STEP - MOVING THINGS AROUND |
|
||||||
|
\-----------------------------------/
|
||||||
|
|
||||||
The first step in building either version of NetHack is to execute
|
The first step in building either version of NetHack is to execute
|
||||||
sys\winnt\nhsetup.bat.
|
sys\winnt\nhsetup.bat to move some files to their required locations.
|
||||||
|
|
||||||
From the command prompt:
|
From the command prompt:
|
||||||
cd sys\winnt
|
cd sys\winnt
|
||||||
@@ -69,11 +71,13 @@ moved there.
|
|||||||
|
|
||||||
If you wish to build from the command line, proceed to "BUILDING FROM
|
If you wish to build from the command line, proceed to "BUILDING FROM
|
||||||
THE COMMAND LINE."
|
THE COMMAND LINE."
|
||||||
|
|
||||||
If you wish to build using Visual C's IDE, proceed now to "BUILDING
|
If you wish to build using Visual C's IDE, proceed now to "BUILDING
|
||||||
USING VISUAL C'S IDE."
|
USING VISUAL C'S IDE."
|
||||||
|
|
||||||
|
/--------------------------------\
|
||||||
BUILDING FROM THE COMMAND LINE
|
| BUILDING FROM THE COMMAND LINE |
|
||||||
|
\--------------------------------/
|
||||||
|
|
||||||
You can built two different versions of NetHack for Win32 from the
|
You can built two different versions of NetHack for Win32 from the
|
||||||
command line:
|
command line:
|
||||||
@@ -95,7 +99,7 @@ I. Dispelling the Myths:
|
|||||||
|
|
||||||
We have provided a Makefile for each of the following compilers:
|
We have provided a Makefile for each of the following compilers:
|
||||||
|
|
||||||
o Microsoft Visual C++ V6.0 SP3 or greater
|
o Microsoft Visual C++ V6.0 SP3, Visual C++ 2005 w/Platform SDK
|
||||||
o Borland C 5.5.1
|
o Borland C 5.5.1
|
||||||
o MinGW 2.0 (with GCC 3.2)
|
o MinGW 2.0 (with GCC 3.2)
|
||||||
|
|
||||||
@@ -119,17 +123,28 @@ II. To compile your copy of NetHack on a Windows NT/2000/XP machine:
|
|||||||
|
|
||||||
Setting Up
|
Setting Up
|
||||||
|
|
||||||
1. It almost goes without saying that you should make sure that your
|
1. It almost goes without saying that you should make sure that your
|
||||||
tools are set up and running correctly. That includes ensuring that
|
tools are set up and running correctly. That includes ensuring that
|
||||||
all the necessary environment variables for the compiler environment
|
all the necessary environment variables for the compiler environment
|
||||||
are set correctly. (Examples: For the Microsoft compiler by
|
are set correctly. For Visual C++ 6.x, you need to execute
|
||||||
executing vcvars32.bat, which is probably in the bin directory of
|
vcvars32.bat which is probably in the bin directory of your compilers
|
||||||
your compilers directory tree. For the Borland Makefile, you can
|
directory tree. If you are using the Visual C++ 2005 Express Edition,
|
||||||
simply invoke the Make utility from the Makefile's directory (For
|
you will need to download and install the MS Platform SDK as well.
|
||||||
the standard Borland compiler installation you can just use the
|
The Platform SDK is required for building native WIN32 applications,
|
||||||
explicit path "c:\borland\bcc55\bin\make /f Makefile.bcc". For the
|
such as this. The two must be integrated to work together. At the
|
||||||
GCC Makefile, add <mingw>\bin to your path, where <mingw> is your
|
time of this writing, there were instructions available from the
|
||||||
MinGW root directory.)
|
manufacturer at the following URL:
|
||||||
|
http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/
|
||||||
|
|
||||||
|
For the GCC Makefile, add <mingw>\bin to your path, where <mingw>
|
||||||
|
is your MinGW root directory.).
|
||||||
|
|
||||||
|
For the Borland Makefile, you can simply invoke the Make utility
|
||||||
|
from the Makefile's directory (For the standard Borland compiler
|
||||||
|
installation you can just use the explicit path
|
||||||
|
"c:\borland\bcc55\bin\make /f Makefile.bcc". NetHack 3.5.0 has not
|
||||||
|
yet been tested with the Borland compiler.
|
||||||
|
|
||||||
|
|
||||||
2. Make sure all the NetHack files are in the appropriate directory
|
2. Make sure all the NetHack files are in the appropriate directory
|
||||||
structure. You should have a main directory with subdirectories
|
structure. You should have a main directory with subdirectories
|
||||||
@@ -266,8 +281,9 @@ Notes:
|
|||||||
|
|
||||||
To run NetHack, proceed to RUNNING NETHACK.
|
To run NetHack, proceed to RUNNING NETHACK.
|
||||||
|
|
||||||
|
/--------------------------------\
|
||||||
BUILDING USING VISUAL C'S IDE
|
| BUILDING USING VISUAL C's IDE |
|
||||||
|
\--------------------------------/
|
||||||
|
|
||||||
Only the Win32 native port built on the Windows API, or Graphical
|
Only the Win32 native port built on the Windows API, or Graphical
|
||||||
NetHack, can be built using the Visual C IDE.
|
NetHack, can be built using the Visual C IDE.
|
||||||
@@ -275,7 +291,7 @@ NetHack, can be built using the Visual C IDE.
|
|||||||
I. Dispelling the Myths:
|
I. Dispelling the Myths:
|
||||||
|
|
||||||
Compiling NetHack using the Visual C IDE is straightforward, as long
|
Compiling NetHack using the Visual C IDE is straightforward, as long
|
||||||
as you have your compiler and tools correctly installed.
|
as you have your compiler and tools correctly installed.
|
||||||
|
|
||||||
It is again assumed that you already changed your directory to
|
It is again assumed that you already changed your directory to
|
||||||
sys\winnt and executed:
|
sys\winnt and executed:
|
||||||
@@ -291,7 +307,18 @@ Setting Up
|
|||||||
1. It almost goes without saying that you should make sure that your
|
1. It almost goes without saying that you should make sure that your
|
||||||
tools are set up and running correctly. (For the Microsoft Visual C
|
tools are set up and running correctly. (For the Microsoft Visual C
|
||||||
IDE it should correctly fire up when you choose it in your Start |
|
IDE it should correctly fire up when you choose it in your Start |
|
||||||
Programs menus.)
|
Programs menus.)
|
||||||
|
|
||||||
|
If you are using Visual C++ 2005 Express Edition, you must install
|
||||||
|
both the Visual C++ 2005 Express Edition, and the Platform SDK.
|
||||||
|
They are both freely downloadable at the time of this writing, but
|
||||||
|
be warned that they are very large downloads. After installing the
|
||||||
|
Visual C++ 2005 Express Edition, you will then need to install the
|
||||||
|
Platform SDK and integrate it with Visual C++ 2005 Express Edition
|
||||||
|
in order to be able to build native WIN32 applications. At the time
|
||||||
|
of this writing, there was some assistance on how to integrate the
|
||||||
|
two products at the following URL:
|
||||||
|
http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/
|
||||||
|
|
||||||
2. Make sure all the NetHack files are in the appropriate directory
|
2. Make sure all the NetHack files are in the appropriate directory
|
||||||
structure. You should have a main directory with subdirectories
|
structure. You should have a main directory with subdirectories
|
||||||
@@ -342,43 +369,53 @@ Setting Up
|
|||||||
as explained above. However, the IDE build has full game
|
as explained above. However, the IDE build has full game
|
||||||
functionality and is the officially released build.
|
functionality and is the officially released build.
|
||||||
|
|
||||||
Start the Visual C IDE. In the Visual C IDE menus, choose:
|
Start the Visual C IDE.
|
||||||
|
In the Visual C++ V6.0 IDE menus, choose:
|
||||||
File | Open Workspace
|
File | Open Workspace
|
||||||
|
In the Visual C++ 2005 Express Edition IDE menus, choose:
|
||||||
|
File | Open Project/Solution
|
||||||
|
|
||||||
|
|
||||||
4. Set up for the build.
|
4. Set up for the build.
|
||||||
|
|
||||||
In the Visual C "Open Workspace" dialog box, navigate to the top of
|
In the Visual C dialog box, navigate to the top of
|
||||||
your NetHack source directory.
|
your NetHack source directory.
|
||||||
|
|
||||||
In there, highlight "nethack.dsw" and click on Open.
|
In there, highlight "nethack.dsw" for Visual C++ 6.0, or
|
||||||
Once the workspace has been opened, you should see the following
|
"nethack.sln" for Visual C++ Express Edition and click on Open.
|
||||||
list in the Visual C selection window:
|
Once the workspace or solution has been opened, you should see
|
||||||
+ dgncomp files
|
the following list in the Visual C selection left pane:
|
||||||
+ dgnstuff files
|
+ dgncomp
|
||||||
+ dlb_main files
|
+ dgnstuff
|
||||||
+ levcomp files
|
+ dlb_main
|
||||||
+ levstuff files
|
+ levcomp
|
||||||
+ makedefs files
|
+ levstuff
|
||||||
+ nethackw files
|
+ makedefs
|
||||||
+ recover files
|
+ nethackw
|
||||||
+ tile2bmp files
|
+ recover
|
||||||
+ tilemap files
|
+ tile2bmp
|
||||||
+ uudecode files
|
+ tilemap
|
||||||
|
+ uudecode
|
||||||
|
|
||||||
On the Visual C menus, choose:
|
On the Visual C++ 6.0 menus, choose:
|
||||||
Project | Set Active Project | NetHackW
|
Project | Set Active Project | NetHackW
|
||||||
|
or for Visual C++ 2005 Express Edition, highlight 'nethackw' and
|
||||||
|
select:
|
||||||
|
Project | Set as Startup Project
|
||||||
|
|
||||||
On the Visual C menus again, choose either:
|
On the Visual C 6.0 menus again, choose either:
|
||||||
Build | Set Active Configuration | NetHackW - Win32 Release
|
Build | Set Active Configuration | NetHackW - Win32 Release
|
||||||
or
|
or
|
||||||
Build | Set Active Configuration | NetHackW - Win32 Debug
|
Build | Set Active Configuration | NetHackW - Win32 Debug
|
||||||
|
In Visual C++ 2005 Express Edition, you can just choose "Debug" or
|
||||||
|
"Release" right on the menu in the "solutions configuration" box.
|
||||||
|
|
||||||
The first will create the Release build of NetHackW which does not
|
The first Release build of NetHackW which does not contain all the
|
||||||
contain all the debugging information and is smaller, and runs
|
debugging information and is smaller, and runs slightly quicker.
|
||||||
quicker. The second will create the Debug build of NetHackW and
|
The Debug build of NetHackW will spend time writing debug information
|
||||||
will spend a lot of time writing debug information to the disk as
|
to the disk as the game is played. Unless you are debugging or
|
||||||
the game is played. Unless you are debugging or enhancing NetHack
|
enhancing NetHack for Windows, you probably will want to choose the
|
||||||
for Windows, choose the Release build.
|
Release build.
|
||||||
|
|
||||||
Building
|
Building
|
||||||
|
|
||||||
@@ -394,7 +431,9 @@ Building
|
|||||||
all the support files that it needs.
|
all the support files that it needs.
|
||||||
|
|
||||||
|
|
||||||
RUNNING NETHACK
|
/-----------------\
|
||||||
|
| RUNNING NETHACK |
|
||||||
|
\-----------------/
|
||||||
|
|
||||||
I. Checking the installation:
|
I. Checking the installation:
|
||||||
Make sure all of the support files -- Guidebook.txt, license,
|
Make sure all of the support files -- Guidebook.txt, license,
|
||||||
|
|||||||
Reference in New Issue
Block a user