changeset 90:c9c6bb34734d

rogue3: update the installation instructions.
author John "Elwin" Edwards
date Sat, 24 Aug 2013 14:07:16 -0700
parents 84651832f967
children e5ddbaf324d4
files rogue3/INSTALL.txt
diffstat 1 files changed, 15 insertions(+), 11 deletions(-) [+]
line wrap: on
line diff
--- a/rogue3/INSTALL.txt	Sat Aug 24 13:50:15 2013 -0700
+++ b/rogue3/INSTALL.txt	Sat Aug 24 14:07:16 2013 -0700
@@ -14,19 +14,23 @@
 with dgamelaunch and security for multiple players.
 
 Installing
-First, configure for your system by editing machdep.h.  The defaults are for a 
-system-wide installation, which will require setgid on the binary.  For a 
-single-user installation, comment out SAVEDIR and set SCOREFILE and LOGFILE to 
-locations somewhere in your home directory.  (That's probably the best thing to 
-do on Windows, too.)
+Rogue V3 now uses autotools.  Run 'autoreconf' and then './configure' to
+configure for your system.  Once that's finished, compile by running make.  (I
+haven't tested the Visual Studio project files on Windows, but they should
+work.)
+
+If you don't use any options with './configure', rogue3 will keep the high
+score list in whatever directory you run it from.  If you just want to play 
+the game yourself, this will work.
 
-Once that's finished, compile by running make.  (I haven't tested the Visual 
-Studio project files on Windows, but they should work.)
+If you want multi-user play, use the '--enable-setgid' and '--enable-savedir'
+options to 'configure'.  After compiling, install the rogue3 binary with setgid
+games.  You will need to make sure that the save directory exists and that
+savefiles, the scorefile, and the logfile can be created and written by the
+games group (assuming you want those features.)
 
-If you want multi-user play, install the rogue3 binary with setgid games.  You 
-will need to make sure that SAVEDIR exists and that savefiles, SCOREFILE, and 
-LOGFILE can be created and written by the games group (assuming you want those 
-features.)  For a single user, installing shouldn't be necessary.
+There are other possible features, including wizard (debugging) mode.  To see
+the full list, run './configure --help'.
 
 Playing
 For more details, see readme36.html (contains the man page) and rogue36.html