Directions for installation:

Note: Crossfire uses a great deal of floating point, and expects the syntax
to be 'x.y'.  In some environments, the language may be dfferent, so that
the format for floats is 'x,y' or something similar.  If this is the
situation for you, you need to change your environment so that floats are in
the 'x.y' format.

1) You need to meet the following requirements:
  A) 3 to 5 Megabytes of free disk space for object files (note that
  uncompress map files will take a lot more)
  B) A compiler that understands ANSI.

  If you don't meet both these requirements, you will be unable to proceed
  further.

2) Run the 'configure' script.  You will need to supply a -prefix=path
   for the program to install into.

   By default, it will create a bin, lib & man directory in the path
   provided.  There are many files in lib, so I do not suggest
   it be a shared lib (ie, /usr/games/lib would be a bad place, but
   /usr/games/lib/crossfire should be OK).

   The standard configure options can be given to specify a location
   (--prefix=/path, --libdir=/path, --bindir, and --mandir)

   All file paths should start with '/'.  Don't use relative filepaths.

   The configure step should create all the necesary makefiles.  Look
   at the output and note any errors - if you get errors during the
   configure stage, there is little point in going further

3) Run 'make depend'.  This should prevent any inconsistent data and
   cause proper remakes if you change the config.h file or re-run
   configure.

4) Edit include/config.h.
   Most options should be fairly well commented.
   The default config.h file should have pretty sane values, and you should
   be able to use it unchanged.

4a) Note that many of the perl programs assume that perl is located as
  /usr/local/bin/perl - if it is someplace else, you will need to go through
  and update the scripts (or probably easier is make a symlink in 
  /usr/local/bin to where your perl is located.)  I don't believe any of
  these scripts are run as the normal compilation & installation process,
  so this is only a real problem if you plan to rebuild the archetypes.

5) Compile the program:  type 'make'.  It should take a little while.  If
   you get errors that abort the compile, copy them down (either using cut
   and paste, or redirect the output of the compile to a file), and send
   those to the bug alias (crossfire-bugs@ifi.uio.no), along with what
   machine type & OS you are using.  Also, include the compile line with its
   various options.  A message saying 'it failed to compile main.c' tells me
   little, and I can not fix problems with that little detail.

6) Install the program by running 'make install'

7) You may want to set the uid or gid bit on the crossfire executable.
   To do this, type either 'chmod u+s' or 'chmod g+s', with the filename
   being the installed version of crossfire.  The highscore file and
   player directory should have their permissions set appropriately.  This
   is only needed if other people may be running the the executable.

8) If you don't have maps, you will need them.  Grab them off the ftp
   site, and unpack them.  Probably easiest to unpack them into the 
   installed lib directory directory, and save an installation procedure.
   
9) You can compress/gzip all files in and below the LIBDIR.  Performance of
   compressing various files may very.  Several files are only read during
   startup, so compressing them will not affect game performance once running.

10) It might be useful to edit "lib/motd" (MessageOfToDay) file.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
COMMON PROBLEMS:

P) When I start the game, the display comes up fine, but the map is filled
with funny characters (demons where buildings should be, etc).

S) The font that is being used does not match the archetypes.  This is
typically because an old version of the font is being used.  Make sure the
new font is installed, and that it is the font being used (there may
be several directories in the fontpath.  The font to be used comes
first.)  Otherwise, you can run the program with -pix or, if
it was compiled in, -xpm mode.  This doesn't use the font.

 Also, I have noticed (At least with X11R6) that if a program is using
an old version of the font, when another program is run that uses
the same font name, it will also get the old version of the font.
(This typically happens when I have a copy of crossedit running,
and then install a new font, and then run crossfire.  Crossfire uses
the font that crossedit is using.)  This is a bug/feature of X11, and
not crossfires error.

If not using fonts, it means that an old version of the crossfire.cfb
or crossfire.pix.? files is being used. Install the new ones (make
install will do the job)

------------------------------------------------------------------------------
P) The server complains that ../lib/unique-items/??? does not exist, and
the game crashes shortly there after.

S) Just create the directory.  It should be created by the make install
process, however, if installing by hand, it may be missing.
------------------------------------------------------------------------------
P) I can't compress/gzip the crossfire.pix files.  If I do, when I
try to run with -xpm, I get errors.

S) Two possible problems:
  1) You are using an older version of the XPM library that does not
     support decompressing of the files when loading.  Upgrade a newer
     version of XPM.
  2) In the case of gzip'd files, it is possible that the user that
     the server is running under does not have gzip/gunzip in its
     path.  Add the directory that gzip resides in to that users
     environmental path.  In csh, something like:

     setenv PATH ${PATH}:/usr/local/bin

     This will add /usr/local/bin (likely place for gzip to be installed)
     to the path.

------------------------------------------------------------------------------
P) It can't find the file stdarg.h, and thus the compile fails.

S) If using gcc, stdarg.h should be installed as part of the normal
installation (with fixincludes).  If it is missing, gcc was not installed
correctly.

It is also possible that you are using an old version of gcc that does not
have stdarg as part of its include files.  Newer versions have this
file.

------------------------------------------------------------------------------

P) I am using Openwindows (or perhaps other windowing system), and
during the compiling of crossedit, it complains about it not being
able to find some header files, like Xaw/Panner.h

S) This is a problem in Openwindows 2, in which those header files
are not included (I don't think the library is either).  The only solution
is to upgrade to another windowing system (X11R5, X11R6, or Openwindows
3).

The other solution is just to not compile crossedit.  It is not needed
to play the game, only to edit/create maps.  To do this, you remove
the crossedit entry from the SUBDIRS line, and go back to stage
3 of the make process (where you make all the Makefiles).

------------------------------------------------------------------------------
P) I can not save characters.

S) 
1) The player save directory was not created.  make install will create
this directory, but if you did not use make install, this could be the
problem.  You can create the directory by hand by doing
'mkdir LIBDIR/players', where LIBDIR is the library directory
that you set in crosssite.def

2) The save directory's permissions are not set properly for the uid/gid
that crossfire is running under.  Situtation that may have caused
this is that 'mark' installed the program, but 'frank' is running
the program, either at the shell prompt, or because the program
has been chmod u+s with frank's id.

------------------------------------------------------------------------------
P) Other problems with XPM mode:
   A) when displaying to an openwindows system with greyscale, it can not
      create the XPM files (note, just openwindows or greyscale may be the
      problem)
   B) When display xpm mode to another machine (Linux), the images are
      not drawn correctly.

S) Both of these problems were seen, and the cause was using an
old XPM library.  If you are having problems of any sort with the XPM
images, please make sure you are using the latest xpm library - this
could be the problem (as of this writing (12/29/94) the newest
version is 3.4c

------------------------------------------------------------------------------
P) When I try to compile, it comlains that it is missing rplay.h

S) rplay.h is part of the rplay package.  You either need to install this
package, or comment out the SoundEffects line in the crosssite.h file.
------------------------------------------------------------------------------
P) I have problems compiling on HP/UX systems.

S) Use gcc - the standard cc with HP/UX apparantly will not compile
crossfire correctly.

------------------------------------------------------------------------------
Other problems?  See the section REPORTING BUGS in the README file.  Follow
all instructions there when submitting a bug report.  If you do not, and
provide insufficient information for me to help out, I will likely just mail
you back telling you to follow those instructions.
