Installation
************

This file documents the installation of GNUstep, `gnustep'.  Copyright
(C) 1998 Free Software Foundation, Inc.  You may copy, distribute, and
modify it freely as long as you preserve this copyright notice and
permission notice.

   This is version 0.5.0 of GNUstep.

   This package contains the core GNUstep libraries. You may need to
install other packages in order to use GNUstep. Read the file
GNUstep-HOWTO for instructions on how to install a complete GNUstep
system.  GNUstep-HOWTO is located in this distribution in
`base/GNUstep-HOWTO' and also is located at the same ftp sites as this
package.

Installing `gnustep'
====================

   Here is a quick-and-dirty example of installation commands:

     ./configure --prefix=/usr/GNUstep
     make
     make install

   Here are more detailed instructions.

  1. Install `gcc'.  The library requires gcc version 2.8.0 or later.

  2. Install the `TIFF' library.  This library requires the header files
     in the TIFF library to compile; the TIFF library is used for the
     NSImage and associated classes for reading, writing, and
     manipulating tiff files.  You should have at least version
     3.4 of libtiff.

  3. Install `DGS'.  You should have at least version 0.5.0; likewise,
     you could just install the DPS client library itself in which use
     version {No Value For "GNUSTEP-DPSCLIENT"}. You system may already
     come with a Display PostScript system.  In that case GNUstep will
     use that system if you desire.

  4. Configure the package for your system.  In the directory that this
     file is in, type `./configure'.  If you're using `csh' on an old
     version of System V, you might need to type `sh configure' instead
     to prevent `csh' from trying to execute `configure' itself.

     By default, `make install' will install the package's files in
     `/usr/GNUstep', unless the environment variable
     `$GNUSTEP_SYSTEM_ROOT' is set.  You can specify an installation
     prefix other than this by giving `configure' the option
     `--prefix=PATH'.

     If your system requires unusual options for compilation or linking
     that `configure' doesn't know about, you can give `configure'
     initial values for some variables by setting them in the
     environment.  In Bourne-compatible shells, you can do that on the
     command line like this:
          CC='gcc -traditional' LIBS=-lpthread ./configure

     The `make' variables that you might want to override with
     environment variables when running `configure' are:

     (For these variables, any value given in the environment overrides
     the value that `configure' would choose:)
    `CC'
          C compiler program.  Default is `cc', or `gcc' if `gcc' is in
          your PATH.

    `INSTALL'
          Program to use to install files.  Default is `install' if you
          have it, `install.sh' otherwise.

     (For these variables, any value given in the environment is added
     to the value that `configure' chooses:)
    `LIBS'
          Libraries to link with, in the form `-lfoo -lbar ...'.

     If you need to do unusual things to compile the package, we
     encourage you to figure out how `configure.in' could check whether
     to do them, and mail diffs or instructions to the address given in
     the `README' so we can include them in the next release.

  5. Type `make' to compile the package.  Alternatively, if you are
     short on disk space, you can `make', `make install', and `make
     clean' each library individually (be sure you do it in the correct
     order - see the GNUmakefile for the correct order).

  6. Type `make install' to install the library, data files, header
     files, and documentation.

  7. You can remove the program binaries and object files from the
     source directory by typing `make clean'.  To also remove the
     Makefile(s), and `config.status' (all the files that `configure'
     created), type `make distclean'.


