Directions for installation.

1) You need to meet the following requirements:
  A) 3 to 5 Megabytes of free disk space for object files (not 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) Edit the config/crosssite.def file.  Most things should be self
   explanatory.  config/madhatter-site.def is an example file of the
   crosssite.def file
   If your local c-compilator doesn't unserstand ANSI-C, then change
   forceCC in config/crosssite.def to an ansi-compilator (for instance
   gcc -ansi).
   All file paths should start with '/'.  Don't use relative filepaths.
   Also, the paths leading up to FONTDIR should be readable.
   When you have customised the crosssite.def file to your local
   system, you can put a copy in the directory which contains the
   crossfire-0.9x.x directories, and it will take precedence over
   the distributed config/crosssite.def.  You should still look over the
   new one, to see if any options have been added, or if the way old options
   are handled has changed.

3) Make the makefiles.  This will be required any time the crosssite.def
   file is changed.
   A) cd into the top level (the directory that contains this file.)
   B) type 'xmkmf', or 'xmkmf.ansi' if you have it.  If you lack xmkmf,
      try 'imake -DUseInstalled -I/usr/lib/X11/config'.  If you lack
      imake, there is probably little hope.

      If you are running X11R6, you can do 'xmkmf -a'.  This will perform
      actions C and D below, and you can go directly to step 4.

   C) type 'make Makefiles'
   D) type 'make depend'  You can ignore any warnings about
      files not found by makedepend.

4) Edit include/config.h.
   Most options should be fairly well commented.  Note that in some cases,
   the options in config.h will not be used, and are instead overridden by
   the options set in the crosssite.def file.
   The default config.h file should have pretty sane values, and need
   little change.

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 me (master@rahul.net), 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:
   A) make install
   B) make install.man
   Note that if you chose the destination directory to be the same as
   the directory you are compiling in, the install will fail (because
   cp will not copy to the same file.)

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.

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 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.

------------------------------------------------------------------------------
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.

------------------------------------------------------------------------------
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.
