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

  To compile and install Dvipsk:

   * Examine `./MACHINES' for system-dependent information.

   * Run `sh configure' in the top-level directory.  This tries to
     figure out system dependencies and the installation prefix.  *Note
     The `configure' script: (kpathsea)configure, for options and other
     information about `configure'.

   * If necessary, edit the paths or other definitions in the files
     `dvipsk/Makefile' and in `dvipsk/c-auto.h' which `configure'
     created.

   * Run `make'; e.g., just type `make' in the top-level directory.
     Barring configuration and compiler bugs, this will compile all the
     programs.

   * Update the paths in `MakeTeXPK', unless you do not want automatic
     font generation (in which case you should not install `MakeTeXPK'
     at all).  *Note Font Generation::.  The `MakeTeXPK' in the
     distribution will only overwrite the installed file if the latter
     contains the string `original MakeTeXPK --'. If your `MakeTeXPK'
     fails, *note Unable to Generate Fonts::..

   * Update the device parameters (available memory, resolution, etc.)
     in `config.ps'.  This file is installed as the system-wide
     configuration file.  *Note Config File Options::.  The `config.ps'
     in the distribution will only overwrite the installed file if the
     latter contains the string `original config.ps --'.

   * Install the programs and supporting macros, fonts, and data files
     with `cd dvipsk; make install'.  Do `make install' in the top-level
     distribution directory only if you also want to install the
     path-searching library, not just Dvipsk.

   * If you want to use more than one device, create configuration
     files for each and install them.

  If you encounter problems, report them to `tex-k@cs.umb.edu'.  To get
on this mailing list, email `tex-k-request@cs.umb.edu' with a message
whose body contains a line
     subscribe YOUR-PREFERRED-EMAIL-ADDRESS

Include the version number of Dvipsk, the system you are using, and
enough information to reproduce the bug in your report.

  To avoid wasted effort and time (both mine and yours), I strongly
advise applying the principles given in the GNU C manual (*note
Reporting Bugs: (gcc)Bugs.) to your bug reports for any software.

  Please also report bugs in this documentation--not only factual
errors, but unclear explanations, typos, wrong fonts, ....

