   This is the INSTALL file for psfilt.

   The process is pretty standard, except for defaults.h and
ppd/ghost{script,view}.ppd, so experienced users may just search this
file for them.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation, and
creates the makefile.  It also creates a file `config.status'
that you can run in the future to recreate the current configuration.

To compile psfilt:

1.  There are some settings that are hard to find automatically.

   Copy defaults.h-dist to defaults.h and edit it to fit your system
   and your preferences.

2.  Configure psfilt for your system.

   Normally, you just `cd' to the directory containing the psfilt
source code and 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.

   Running `configure' takes 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 psfilt 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
the `configure' script.  `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, `gmake install' will install psfilt and its manual page
in `/usr/local/bin' and `/usr/local/man'.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.  Alternately, you can do so by consistently
giving a value for the `prefix' variable when you run `gmake', e.g.,
     gmake prefix=/usr/gnu
     gmake prefix=/usr/gnu install

   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 `gmake'
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 same prefix.

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

   On systems that require unusual options for compilation or linking
that the package's `configure' script does not know about, you can give
`configure' initial values for 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=-lposix ./configure

   Here are the `gmake' variables that you might want to override with
environment variables when running `configure'.

   For these variables, any value given in the environment overrides the
value that `configure' would choose:

 - Variable: CC
     C compiler program.  The default is `gcc'.

 - Variable: INSTALL
     Program to use to install files.  The default is `install' if you
     have it, `cp' otherwise.

   For these variables, any value given in the environment is added to
the value that `configure' chooses:

 - Variable: DEFS
     Configuration options, in the form `-Dfoo -Dbar...'.

 - Variable: LIBS
     Libraries to link with, in the form `-lfoo -lbar...'.

   If you need to do unusual things to compile the package, I 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 I
can include them in the next release.

3.  Type `gmake' to compile the package.  If you want, you can override
the `gmake' variables CFLAGS and LDFLAGS like this:

	gmake CFLAGS=-O2 LDFLAGS=-s

4.  Type `gmake install' to install programs, data files, and
documentation.

    You might want to put ppd/ghost{script,view}.ppd in some publicly
accessible place that is covered by DEFAULT_PPDPATH.

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

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