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

This file documents the installation of the Display Ghostscript System,
`DGS'.  Copyright (C) 1996-98 Free Software Foundation, Inc.  You may
copy, distribute, and modify this file freely as long as you preserve
this copyright notice and permission notice.

Installing `DGS' version 0.5.10
===============================

   You need the following packages before you try to install `DGS':

  1. ghostscript-fonts.  Fonts do not come with the `DGS' package, you
     need to get these separately from the same place you got the `DGS'
     package, or from ftp.gnu.org or it's mirrors, or the Ghostscript
     site `http://www.cs.wisc.edu/~ghost/index.html'

  2. The Z compression/decompression library.  This library is already
     available on many GNU systems. The configuration script will tell
     you if it cannot find the library. If you need it, you can get it
     from the same place you got the `DGS' package, or the latest
     version from `ftp://ftp.cdrom.com/pub/infozip/zlib/zlib.tar.gz'.

  3. The PNG library.  This library is already available on many GNU
     systems. The configuration script will tell you if it cannot find
     the library. If you need it, you can get it from the same place
     you got the `DGS' package, or the latest version from
     `ftp://swrinde.nde.swri.edu/pub/png/src'.

  4. The glib library, Version 1.2.2 or greater.  This library is
     already available on many GNU systems. The configuration script
     will tell you if it cannot find the library. If you need it, you
     can get it from `http://www.gtk.org'

  5. The JPEG library SOURCE files.  The library is already available
     on many GNU systems. However to build `DGS', SOURCE code of the
     library is needed. Most `DGS' distributions already include this
     code in a directory named jpeg.  You can get the library from
     `ftp://ftp.uu.net/graphics/jpeg/'.  See also gs/Make.htm and
     gs/gcc-unix.mak.in.


   Installation instructions:

  1. Compile and install the zlib library, the png library, and the glib
     library, if you do not already have them.

  2. Put the JPEG library source directory to `DGS' directory or
     somewhere else, if you do not already have the JPEG library in the
     `DGS' directory.

     If you add the JPEG library source directory to the `DGS'
     directory, you must rename the directory to `jpeg'.  For example,
     if you get the JPEG library source files from
     `ftp://ftp.uu.net/graphics/jpeg/', the file name is
     jpegsrc.v6b.tar.gz. Make the `DGS' directory current, then
     uncompress and unpack the archive, creating a directory named
     jpeg-6b.  Rename jpeg-6b to jpeg.

     If you put the JPEG library source elsewhere than the `DGS'
     directory, tell the configure script (described below) the place
     using the `--with-jpeg-src-prefix=JPATH' option.

  3. 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.  Read
     the generic installation instructions below for more options.

  4. Type `make' to compile the package.

  5. Type `make install' to install programs, data files, and
     documentation.

  6. After installing the programs, you need to install ghostscript
     fonts.  Change to the directory `prefix/share/ghostscript/fonts',
     where `prefix' is the root directory that the programs are
     installed in.  You may have specified this on the command line
     when you invoked configure, with the `--prefix' argument,
     otherwise it is in some default location, like `/usr', or
     `/usr/local'.  From here, unpack/untar the fonts package into this
     directory.

     Note: If you are installing `DGS' into the GNUstep directory
     structure, the fonts go in a different place. See the section
     below on installing `DGS' into the GNUstep directory structure.

  7. See if things work by trying a test program. Type:

          texteroids "A Cute String"

     and see what happens. Good Luck!


Generic installation/configuration instructions:
================================================

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

     The `configure' shell script attempts to guess correct values for
     various system-dependent variables used during compilation, and
     creates the Makefile(s) (one in each subdirectory of the source
     directory).  In some packages it creates a C header file
     containing system-dependent definitions.  It also creates a file
     `config.status' that you can run in the future to recreate the
     current configuration.

     Running `configure' takes less than a minute or two.  While it is
     running, it prints some messages that tell what it is doing.  If
     you don't want to see the messages, run `configure' with its
     standard output redirected to `/dev/null'; for example:
          ./configure >/dev/null

     To compile the package in a different directory from the one
     containing the source code, you must use a version of make that
     supports the VPATH variable, such as GNU make.  `cd' to the
     directory where you want the object files and executables to go
     and run `configure'.  `configure' automatically checks for the
     source code in the directory that `configure' is in and in `..'.
     If for some reason `configure' is not in the source code directory
     that you are configuring, then it will report that it can't find
     the source code.  In that case, run `configure' with the option
     `--srcdir=DIR', where DIR is the directory that contains the
     source code.

     By default, `make install' will install the package's files in
     /usr/local/bin, /usr/local/lib, /usr/local/man, etc.  You can
     specify an installation prefix other than /usr/local by giving
     `configure' the option `--prefix=PATH'.  Alternately, you can do
     so by giving a value for the `prefix' variable when you run
     `make', e.g.,
          make prefix=/usr/gnu

     You can specify separate installation prefixes for
     architecture-specific files and architecture-independent files.
     If you give `configure' the option `--exec_prefix=PATH' or set the
     `make' variable `exec_prefix' to PATH, the package will use PATH
     as the prefix for installing programs and libraries.  Data files
     and documentation will still use the regular prefix.  Normally,
     all files are installed using the regular prefix.

     You can tell `configure' to figure out the configuration for your
     system, and record it in `config.status', without actually
     configuring the package (creating `Makefile's and perhaps a
     configuration header file).  To do this, give `configure' the
     `--no-create' option.  Later, you can run `./config.status' to
     actually configure the package.  This option is useful mainly in
     `Makefile' rules for updating `config.status' and `Makefile'.  You
     can also give `config.status' the `--recheck' option, which makes
     it re-run `configure' with the same arguments you used before.
     This is useful if you change `configure'.

     `configure' ignores any other arguments that you give it.

     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' DEFS=-D_POSIX_SOURCE ./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:)
    `DEFS'
          Configuration options, in the form `-Dfoo -Dbar ...'

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

  2. Type `make' to compile the package.  If you want, you can override
     the `make' variables `CFLAGS' and `LDFLAGS' like this:
          	make CFLAGS=-O2 LDFLAGS=-s

  3. Type `make install' to install programs, data files, and
     documentation.

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

     The file `configure.in' is used as a template to create
     `configure' by a program called `autoconf'.  You will only need it
     if you want to regenerate `configure' using a newer version of
     `autoconf'.


Install `DGS' within the GNUstep directory structure.
=====================================================

   If you are using `DGS' in combination with GNUstep then you may
prefer to install `DGS' in the GNUstep directory structure; this can be
easily accomplished when configuring `DGS' by simply specifying the
GNUstep root directory as the prefix.

     ./configure --prefix=$GNUSTEP_SYSTEM_ROOT

   You must already have the GNUstep Makefile Package installed and the
GNUstep environment variables defined.  The file
`$GNUSTEP_SYSTEM_ROOT/share/config.site', which will get processed by
`configure', defines the appropriate Autoconf variables so that the
binaries, libraries and resource files of `DGS' are installed in the
proper locations.

   In this case, the `DGS' programs get installed in
`$GNUSTEP_SYSTEM_ROOT/Tools', and the data files (including fonts) get
installed in `$GNUSTEP_SYSTEM_ROOT/Library/share/ghostscript'.  Be sure
to install the fonts in this location, rather than the one specified in
the previous installation instructions.

