  "I swear by my life and my love of it that I will never live
   for the sake of another man, nor ask another man to live for
   mine"

                    John Galt in "Atlas Shrugged", by Ayn Rand


AUTHOR

  The author is magick@wizards.dupont.com.  This software is NOT
  shareware.  However, I am interested in who might be using it.
  Please consider sending me a picture postcard of the area where you
  live.  Send postcards to

    John Cristy
    P.O. Box 40
    Landenberg, PA  19350
    USA

  I'm also interested in receiving coins or stamps from around the world for
  my collection.


AVAILABILITY

  Xtp is available as

    ftp://ftp.wizards.dupont.com/pub/ImageMagick/delegates/xtp-5.2.tar.gz

  I want xtp to be of high quality, so if you encounter a
  problem I will investigate.  However, be sure you are using the most
  recent version from ftp://ftp.wizards.dupont.com/pub/ImageMagick
  before submitting any bug reports or suggestions.


WWW

  The official ImageMagick WWW page (which includes xtp) is

    http://www.wizards.dupont.com/cristy/ImageMagick.html

UNIX/Cygwin COMPILATION

  Type:

    gzip -dc xtp-5.2.tar.gz | tar xvf -
    cd xtp-5.2

  If you do not have gunzip(1), it is available as
  prep.ai.mit.edu:pub/gnu/gzip-1.2.4.shar.

  Configuring Xtp

    The xtp package is configured via 'configure'.

    If you are willing to accept configure's default options, type:

        ./configure

    and watch the configure script output to verify that it finds
    everything that you think it should. If it does not, then adjust
    your environment so that it does.

    If you are not happy with configure's choice of compiler,
    compilation flags, or libraries, you can give `configure' initial
    values for variables by setting them in the environment.  Using a
    Bourne-compatible shell, you can do that on the command line like
    this:

        CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

    Or on systems that have the `env' program, you can do it like this:

        env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

    The configure variables you should be aware of are:

        CC          Name of C compiler (e.g. 'cc -Xa') to use
        CFLAGS      Compiler flags (e.g. '-g -O2') to compile with
        CPPFLAGS    Include paths (-I/somedir) to look for header files
        LDFLAGS     Library paths (-L/somedir) to look for libraries
                    Systems that support the notion of a library
                    run-path may additionally require -R/somedir or
                    '-rpath /somedir' in order to find shared libraries
                    at run time.
        LIBS        Extra libraries (-lsomelib) required to link

    Any variable (e.g. CPPFLAGS or LDFLAGS) which requires a directory
    path must specify an absolute path rather than a relative path.

    By default, `make install' will install the package's files in
    `/usr/local/bin', `/usr/local/man', etc.  You can specify an
    installation prefix other than `/usr/local' by giving `configure'
    the option `--prefix=PATH'.

    Configure can usually find the X include and library files
    automatically, but if it doesn't, you can use the `configure'
    options `--x-includes=DIR' and `--x-libraries=DIR' to specify their
    locations.

    The configure script provides a number of xtp specific
    options.  When disabling an option --disable-something is equivalent
    to specifying --enable-something=no and --without-something is
    equivalent to --with-something=no.  The configure options are as
    follows (execute 'configure --help' to see all options).

      --enable-socks       enable use of SOCKS 5 library and 'rftp'

    Xtp options represent either features to be enabled or
    packages to be included in the build.  When a feature is enabled
    (via --enable-something), it enables code already present in
    ImageMagick.  When a package is enabled (via --with-something), the
    configure script will search for it, and if is is properly
    installed and ready to use (headers and built libraries are found
    by compiler) it will be included in the build.  The configure script
    is delivered with all features disabled and all packages enabled.

    Building under Cygwin

      Xtp may be built under the Windows NT/'9X Cygwin
      Unix-emulation environment which may be downloaded from
      http://sourceware.cygnus.com/cygwin/.

    Dealing with configuration failures:

      While configure is designed to ease installation of ImageMagick,
      it often discovers problems that would otherwise be encountered
      later when compiling ImageMagick. The configure script tests for
      headers and libraries by executing the compiler (CC) with the
      specified compilation flags (CFLAGS), pre-processor flags
      (CPPFLAGS), and linker flags (LDFLAGS). Any errors are logged to
      the file 'config.log'. If configure fails to discover a header or
      library please review this log file to determine why, however,
      please be aware that *errors in the config.log are normal* because
      configure works by trying something and seeing if it fails. An
      error in config.log is only a problem if the test should have
      worked on your system.. After taking corrective action, be sure to
      remove the 'config.cache' file before running configure so that
      configure will re-inspect the environment rather than using cached
      values.

      Common causes of configure falures are: 1) a header is not
      in the header include path (CPPFLAGS -I option); 2) a 
      library is not in the linker search/run path (LDFLAGS -L/-R
      option); 3) a library is missing a function (old
      version?); 4) compilation environment is faulty.

      If all reasonable corrective actions have been tried and the
      problem appears to be due to a flaw in the configure script,
      please send a bug report to the configure script maintainer
      (currently bfriesen@simple.dallas.tx.us). All bug reports should
      contain the operating system type (as reported by 'uname -a') and
      the compiler/compiler-version. A copy of the configure script
      output and/or the config.log file may be valuable in order to find
      the problem. If you send a config.log, please also send a script
      of the configure output and a description of what you expected to
      see (and why) so the failure you are observing can be identified
      and resolved.

COPYRIGHT

  Copyright (C) 2000 ImageMagick Studio, a non-profit organization
  dedicated to making software imaging solutions freely available.

  Permission is hereby granted, free of charge, to any person obtaining
  a copy of this software and associated documentation files
  ("ImageMagick"), to deal in ImageMagick without restriction,
  including without limitation the rights to use, copy, modify, merge,
  publish, distribute, sublicense, and/or sell copies of ImageMagick,
  and to permit persons to whom the ImageMagick is furnished to do so,
  subject to the following conditions:

  The above copyright notice and this permission notice shall be
  included in all copies or substantial portions of ImageMagick.

  The software is provided "as is", without warranty of any kind,
  express or implied, including but not limited to the warranties of
  merchantability, fitness for a particular purpose and
  noninfringement.  In no event shall ImageMagick Studio be liable for
  any claim, damages or other liability, whether in an action of
  contract, tort or otherwise, arising from, out of or in connection
  with ImageMagick or the use or other dealings in ImageMagick.

  Except as contained in this notice, the name of the ImageMagick
  Studio shall not be used in advertising or otherwise to promote the
  sale, use or other dealings in ImageMagick without prior written
  authorization from the ImageMagick Studio.
