Installing GP
*************

   * For the impatient:

          make install

     where make is GNU make, and GCC and GPC are installed. When
     problems, read on. :-)

   * For the rest of us:

     GP requires GCC, GPC and GNU make.

     GP does *not* use GPC's "automake" feature which it is intended to
     replace, but rather a makefile, so it should build without
     problems also on systems where the "automake" feature does not
     work correctly.

     There is a configure script, but unlike other packages, it is not
     necessary to use it. You can simply call `make'. The makefile
     understands the following targets:

    `all'
          compile program (default)

    `check'
          compile program and run self test

    `install'
          compile and install program, info and config file

    `uninstall'
          uninstall program, info and config file

    `dvi'
          make printable documentation in DVI format

    `ps'
          make printable documentation in PostScript format

    `pdf'
          make printable documentation in PDF format

    `dist'
          create an archive containing the sources

    `fulldist'
          create an archive containing the sources including generated
          files

    `bindist'
          create an archive containing binaries for your platform,
          compiling them if necessary

    `clean'
          remove all compiled files

    `distclean'
          like `clean', but also remove the source and binary archives
          and the configuration data in `Makefile.cfg'

    `extraclean'
          like `distclean', but also remove files that require special
          tools like `lex' or `makeinfo' for rebuilding

     and, among others, the following optional variables which can be
     set with `VARNAME="VALUE"' on the `make' command line:

    `srcdir'
          source directory - not necessary if running make in the source
          directory

    `prefix'
          the base directory in subdirectories `bin', `info' and `etc'
          of which files will be installed (default: `/usr/local';
          `$DJDIR' under DJGPP)

    `TARGET'
          a target machine specification for cross-compiling, only used
          to determine the defaults for `CC' and `PC' (default: nothing)

    `CC'
          C compiler (default: same as Pascal compiler if set, otherwise
          `$(TARGET)gcc')

    `PC'
          Pascal compiler (default: `$(TARGET)gpc')

    `GPC_UNIT_PATH'
          the unit path for GPC's standard units (not necessary to
          specify if GPC was properly installed before)

    `CFLAGS'
          flags used for the C compiler (default: `-O2 -Wall')

    `PFLAGS'
          flags used for the Pascal compiler (default: `$(CFLAGS)')

    `LDFLAGS'
          additional flags for linking (default: `-s')

     If you want to use the configure script, you can get a list of its
     options with `./configure --help'. It understands the usual
     options such as `--prefix', `--srcdir' and `--target'.

     If you want to build GP in a directory other than the source
     directory, using configure is recommended, though also then not
     necessary. If you invoke configure by its full path, it will find
     the source directory automatically.

   * DJGPP:

     Because of short file names and the unsure availability of bash and
     other standard tools, Dos needs a special make process. However,
     the makefile detects DJGPP systems by the presence of the
     environment variables `COMSPEC' and `DJGPP', and handles the
     difference automatically.

     A simple `make install' should work without any of the tools
     (besides GCC, GPC and GNU make), but probably not much more, and it
     was not tested too well.

     Other make targets need some more utilities like `bash', `rm',
     `cp' or `zip' (which must be a DJGPP executable, e.g. `zip32.exe'
     renamed to `zip.exe', because of command line length issues).

   * Other Dos/MS-Windows systems:

     Please let me know what works on which system, or send patches ...


