$Id: INSTALL.txt,v 1.3 1997/11/27 07:44:42 bert Exp $

See contrib/NT/README.txt for instructions

Following are the installation instructions for the 
UNIX version of XPilot.  For the Windows version
see contrib/NT/README.txt for instructions.

To compile XPilot, you'll need at least

An ANSI C compiler
        gcc with gcc-includes installed should work just fine,
        though many default compilers (like Sun's) are NOT
        ANSI C compliant so check and double check that the
        compiler you plan to use is ANSI C compliant.
        About 95% of all the problems reported is because
        users are not using an ANSI C compliant compiler!)

X11     (any revision from R4 up to R6 works OK)

Also note that XPilot isn't gentle with the X server, so a fast machine
(with a graphics accelerator that does line drawing in hardware),
in a fast network is the ideal situation.


INSTALLATION

The complete installation just requires three steps -- geez, how easy
can it be? :)

1. Edit configuration files:

   If you don't have Imake, you'll have to manage with the Makefile.std
   in the src directory; just cd to src, copy Makefile.std to Makefile,
   and edit config.h.

   If you have Imake, you must first

        edit Local.config

   to suit your environment.
   Then issue the following command

        xmkmf -a

   or, if that fails,

        xmkmf ; make Makefiles ; make includes ; make depend


2. Compile:

   Just run

        make

   If you get lots of errors, verify that you're using an ANSI C compiler.

   If you're compiling with gcc and get conflicting types for `abort'
   and `exit', check that your include files has prototypes and if not,
   that you have installed gcc-includes.  You should always install
   gcc-includes if your system include files doesn't have prototypes.
   (As a temporary hack, you may remove #include <stdlib.h> from all
   the files.)


3. Install:

   To install the executables, maps, and textures, run

        make install

   and to install the manual pages, run

        make install.man

   If you have logging enabled you will have to touch a file called
   log in the INSTLIBDIR and give other users write permission to it.
   This is necessary since xpilot isn't, and shouldn't be, set[ug]id.


4. Play:

    Start a server first:

        xpilots -map globe.map

    Then start a client in another window:

        xpilot

    It should find the server automatically.
    Or you can "telnet meta.xpilot.org 4400" to
    find other servers to connect to.

If everything fails, see the FAQ, which you can find in the doc subdirectory.
