  "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

  ImageMagick is available as

    ftp://ftp.wizards.dupont.com/pub/ImageMagick/ImageMagick-5.2.5.tar.gz

  ImageMagick client executables are available for some platforms. See

    ftp://ftp.wizards.dupont.com/pub/ImageMagick/binaries
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/mac
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/nt
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/vms
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/linux

  I want ImageMagick 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.  Report any
  problems via the web-based reporting facility at
  http://www.simplesystems.org/ImageMagick/bugs.html.


WWW

  The official ImageMagick WWW page is

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

  To use display as your external image viewer, edit the global
  mail-cap file or your personal mail-cap file .mailrc (located at your
  home directory) and put this entry:

    image/*; display %s


MAILING LIST

  There is a mailing list for discussions and bug reports about
  ImageMagick.  To subscribe send the message

    subscribe magick

  to majordomo@imagemagick.org.  You will receive a welcome message
  which tells you how to post messages to the list,
  magick@imagemagick.org.


UNIX/Cygwin COMPILATION

  Type:

    gzip -dc ImageMagick-5.2.5.tar.gz | tar xvf -
    cd ImageMagick-5.2.5

  If you do not have gunzip(1), it is available as
  ftp.gnu.org:pub/gnu/gzip-1.2.4.shar.

  Use 'configure' to automatically configure, build, and install
  ImageMagick.

  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 specifying them on the configure command line, e.g.:

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

  The configure variables you should be aware of are:

      CC          Name of C compiler (e.g. 'cc -Xa') to use
      CXX         Name of C++ compiler to use
      CFLAGS      Compiler flags (e.g. '-g -O2') to compile C code
      CXXFLAGS    Compiler flags (e.g. '-g -O2') to compile C++ code
      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 ImageMagick 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-shared[=PKGS]  build shared libraries [default=no]
    --enable-static[=PKGS]  build static libraries [default=yes]
    --enable-lzw            enable LZW support (default is no)
    --enable-16bit-pixel    enable 16 bit/quantum pixels (default is no)
    --with-threads          enable threads support
    --with-cache            set pixel cache threshhold (default 80MB)
    --with-magick_plus_plus enable build/install of Magick++
    --without-frozenpaths   disable frozen delegate paths
    --without-largefiles    disable support for large (64 bit) file offsets
    --without-perl          disable build/install of PerlMagick
    --without-bzlib         disable BZLIB support
    --without-dps           disable Display Postscript support
    --without-fpx           disable FlashPIX support
    --without-hdf           disable HDF support
    --without-jbig          disable JBIG support
    --without-jpeg          disable JPEG support
    --without-png           disable PNG support
    --without-tiff          disable TIFF support
    --without-ttf           disable TrueType support
    --with-ttf-fontpath     set default TrueType font path (default none)
    --without-xml           disable XML support
    --without-zlib          disable ZLIB support
    --with-x                use the X Window System

  ImageMagick options represent either features to be enabled,
  disabled, 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. In general, the
  only reason to disable a package is if a package exists but it is
  unsuitable for the build (perhaps an old version or not compiled with
  the right compilation flags).

  Several configure options require special note:

    o --enable-shared: the shared libraries are built. Shared
      libraries are valuable because they are *shared* across more than
      one invocation of an ImageMagick or PerlMagick client. In
      addition, the clients take much less disk space and shared
      libraries are required in order for PERL to dynamically load the
      PerlMagick extension.

      ImageMagick built with delegates (see MAGICK PLUG-INS below) can
      pose additional challenges.  You can build all the delegates
      statically and link them into the ImageMagick shared library
      (i.e. libMagick.so) or alternatively you can build the delegates
      as shared libraries (some systems already have delegates
      installed as shared libraries).  Shared libraries compilation
      flags differ from vendor to vendor (gcc's is -fPIC).  However,
      you must compile all shared library source with the same flag
      (for gcc use -fPIC rather than -fpic).

    o --disable-static: static archive libraries (with extension .a)
      are not built.  If you are building shared libraries, there is
      little value to building static libraries. Reasons to build
      static libraries include: 1) they can be easier to debug; 2) the
      clients do not have external dependencies (i.e. libMagick.so); 3)
      building PIC versions of the delegate libraries may take
      additional expertise and effort; 4) you are unable to build
      shared libraries.

    o --with-modules: image format coders are built as loadable modules
      which are installed in [prefix]/lib/ImageMagick/modules/coders.
      Support for modules allows the formats supported by ImageMagick
      to be extended by simply adding additional modules to the module
      search path.  The modules option is only available in conjunction
      with --enable-shared.  If --enable-shared is not also specified,
      then support for modules is disabled.

    o --enable-lzw: Unisys reportedly claims a patent on the algorithm
      supporting LZW compression (e.g. used by GIF and TIFF).  To avoid
      possibly infringing on this patent, support for LZW is disabled
      by default.  With LZW support, GIF files written by ImageMagick
      will be much larger than expected.

    o --enable-16bit-pixel: By default ImageMagick represents images
      internally using an eight-bit pixel quantum (red, green, blue,
      and alpha component).  Scientific applications, or other
      specialized applications, which must ensure that the full dynamic
      range of the image pixels is preserved across operations, or
      which must process an image format that can represent deep
      pixels, may want to enable support for sixteen-bit pixel
      quantums. When this option is specified, the definition
      QuantumLeap is applied when ImageMagick is built, allowing RGBA
      values to range from 0 to 65535 rather than 0 to 255.  Enabling
      this option will cause ImageMagick to run about 30% slower.

    o --with-magick_plus_plus: Enable building Magick++, the C++
      application programming interface to ImageMagick.  A suitable C++
      compiler is required. Specify the CXX configure variable to
      select the C++ compiler to use, and CXXFLAGS to select the
      desired compiler opimization and debug flags.

    o --without-frozenpaths: By default, the configure script will
      determine the location of all delegates (external programs) and
      incorporate the full paths within the delegates.mgk file. This is
      the default because it is assumed that the installer's
      environment is appropriately configured and that the operation of
      ImageMagick should not be subject to the end-user's environment.
      However, if it is desirable to allow the end user to define
      their own environment or possible that the end user's environment
      does not match the installer's environment (e.g. for binary
      distributions), --without-frozenpaths may be specified so that
      only the delegate's name is included in the delegates.mgk file.

    o --with-threads: By default, the ImageMagick library is compiled
      without multi-thread support.  This is fine for the utilities,
      and for use in single-threaded applications. When multi-threaded
      applications are to be used with the ImageMagick library, thread
      safety should be selected via --with-threads.  Multi-thread
      support is disabled by default since a thread-safe ImageMagick
      may run slower (OS dependent) due to additional locking within
      the C library (e.g. in malloc()).

    o --with-cache: Specify a different image pixel cache threshold
      using the --with-cache option. When ImageMagick will have more
      image pixel data in memory than the cache threshold setting,
      additional images are cached on disk. Since memory is much faster
      than disk, it is usually better to use memory rather than disk
      for the pixel cache. On large memory machines, the cache
      threshold may be increased to a larger size than the default of
      80MB. Small memory machines may want to decrease the threshold.

    o --without-largefiles: By default, ImageMagick is compiled with
      support for large (> 2GB on a 32-bit CPU) files if the operating
      system supports large files.  All applications which use the
      ImageMagick library must then also include support for large
      files. By disabling support for large files via
      --without-largefiles, dependent applications do not require
      special compilation options for large files in order to use the
      library.

    o --without-perl: By default, PerlMagick is conveniently compiled
      and installed in one step. When --without-perl is specified, you
      must first install ImageMagick, change to the PerlMagick
      subdirectory, build, and finally install PerlMagick. Note,
      PerlMagick is configured even if --without-perl is specified. If
      --enable-shared is not specified, a new PERL interpreter
      (PerlMagick) is built which is statically linked against the
      PerlMagick extension. This new interpreter is installed alongside
      your existing PERL interpreter. If --enable-shared is specified,
      the PerlMagick extension is built as a dynamically loadable
      object which is loaded into your current PERL interpreter at
      run-time. Use of dynamically-loaded extensions is preferable over
      statically linked extensions so --enable-shared should be
      specified if possible. If the argument --with-perl=/path/to/perl
      is supplied, then /path/to/perl will be taken as the PERL
      interpreter to use.

    o --without-x: By default, ImageMagick will use X11 libraries if
      they are available. When --without-x is specified, use of X11 is
      disabled. The display, animate, and import programs are not built
      or installed. The remaining programs have reduced functionality
      such as no access to X11 fonts (consider using Postscript or
      TrueType fonts instead).

  Building under Cygwin

    ImageMagick may be built under the Windows Win2K/'9X Cygwin
    Unix-emulation environment which may be downloaded from
    http://sourceware.cygnus.com/cygwin/. Pre-compiled X11R6.4
    libraries for Cygwin are available from
    http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.4/. Use the
    same procedure as for Unix except that building DLLs is not yet
    supported so do not specify the --enable-shared option to
    configure.

  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 failures are: 1) a delegate header is not
    in the header include path (CPPFLAGS -I option); 2) a delegate
    library is not in the linker search/run path (LDFLAGS -L/-R
    option); 3) a delegate 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.

  To confirm your build of the ImageMagick distribution was successful,
  type:

      display

  If the program faults, ensure that you have not inadvertently linked
  to an older version of the libMagick library or used header files
  from a different release. To ensure this is not the case type

      cd ImageMagick/magick
      make install
      cd ..
      make clean
      make

  If the image colors are not correct use this command:

      display -visual default

  Be sure to read the manual pages for the display(1), animate(1),
  montage(1), import(1), mogrify(1), identify(1), combine(1), and
  convert(1) utilities. Also read the ImageMagick frequently asked
  questions in the file www/Magick.html. This is required reading. Most
  of the questions I get via electronic mail are answered in this
  document.

  Place display(1) X application defaults in
  /usr/lib/X11/app-defaults/Display.  Use the appropriate name for
  other clients (e.g. Animate, Montage, etc).  To execute display(1)
  from as a menu item of any window manager (olwm, mwm, twm, etc), use

      logo:Untitled


MAGICK DELEGATES

  To further enhance the capabilities of ImageMagick, you may want to
  get these programs or libraries:

    o ImageMagick requires the BZLIB library from

	  http://sourceware.cygnus.com/bzip2/index.html

      to read and write BZip compressed MIFF images.

    o ImageMagick requires ralcgm from

	  http://www.agocg.ac.uk/train/cgm/ralcgm.htm

      to read the Computer Graphics Metafile image format (may not
      compile under linux).  You also need Ghostscript (see below).

    o ImageMagick requires fig2dev from

	  ftp://ftp.x.org/contrib/applications/drawing_tools/transfig

      to read the TransFig image format.

    o ImageMagick requires the FreeType software, version 1.1 or above,
      available as

	 http://www.freetype.org/

      to annotate with TrueType fonts.

    o ImageMagick requires Ghostscript software available from

	 http://www.cs.wisc.edu/~ghost/

      to read the Postscript or the Portable Document format.  It is
      used to annotate an image when an X server is not available.  See
      the FreeType library above for another means to annotate an
      image.  Note, Ghostscript must support the ppmraw device (type gs
      -h to verify).  If Ghostscript is unavailable, the Display
      Postscript extension is used to rasterize a Postscript document
      (assuming you define HasDPS).  The DPS extension is less robust
      than Ghostscript in that it will only rasterize one page of a
      multi-page document.

    o ImageMagick requires the NCSA HDF library available via anonymous
    FTP
      as

	  ftp://ftp.ncsa.uiuc.edu/HDF/HDF/HDF_Current

      to read and write the HDF image format.

    o ImageMagick requires hp2xx available from

	  http://www.gnu.org/software/hp2xx/hp2xx.html

      to read the HP-GL image format.

    o ImageMagick requires the LCMS library available from

	  http://www.abaforum.es/martim/lcms.htm

      to perform color management.

    o ImageMagick requires gnuplot available via anonymous FTP as

	  ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot3.5.tar.Z

      to read GNUPLOT plot files (with extension gplt).

    o ImageMagick requires html2ps available from

	  http://www.tdb.uu.se/~jan/html2ps-1.0b1.zip

      to read the HTML image format.

    o ImageMagick requires the JBIG-Kit software available via
    anonymous
      FTP as

	  ftp://ftp.informatik.uni-erlangen.de/pub/doc/ISO/JBIG/

      to read the JBIG image format.

    o ImageMagick requires the Independent JPEG Group's software
      available via anonymous FTP as

	  ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz

      to read the JPEG image format.

      Apply this JPEG patch to Independent JPEG Group's source
      distribution to read lossless jpeg-encoded DICOM images:

	  ftp://ftp.wizards.dupont.com/pub/ImageMagick/delegates/
	    ljpeg-6b.tar.gz

      Concerning iterative JPEG compression:  see Kinoshita and
      Yamamuro, Journal of Imaging Science and Technology, "Image
      Quality with Reiterative JPEG Compression", Volume 39, Number 4,
      July 1995, 306-312 who claim that (1) the iterative factor of the
      repetitive JPEG operation had no influence on image quality, and
      (2) the first compression determined base image quality.

    o ImageMagick requires the MPEG utilities from the MPEG Software
      Simulation Group, which are available via anonymous FTP as

	  ftp://ftp.mpeg.org/pub/mpeg/mssg/mpeg2vidcodec_v12.tar.gz

      to read or write the MPEG image format.

    o ImageMagick requires the PNG library, version 1.0 or above, from

	  http://www.libpng.org/pub/png/pngcode.html

      to read the PNG image format.

    o ImageMagick requires ra_ppm from Greg Ward's Radiance
      software available via anonymous FTP as

	  http://radsite.lbl.gov/radiance/HOME.html

      to read the Radiance image format (may not compile under linux).

    o ImageMagick requires rawtorle from the Utah Raster Toolkit
      available via anonymous FTP as

	  ftp://ftp.cs.utah.edu/pub/dept/OLD/pub/urt-3.1b.tar.Z

      to write the RLE image format (may not compile under linux).

    o ImageMagick requires scanimage from

	  http://www.mostang.com/sane/

      to import image from a scanner device.

    o ImageMagick requires Sam Leffler's TIFF software available
      via anonymous FTP as

	  http://www.libtiff.org/

      to read the TIFF image format.  It in turn optionally requires
      the JPEG and ZLIB libraries.

    o ImageMagick requires wmftogif available from

	  http://www.csn.ul.ie/~caolan/docs/libwmf.html

      to read the Windows Meta File image format.

    o ImageMagick requires wget available via the Web as

	  http://www.gnu.org/software/wget/wget.html

      to read images specified with a World Wide Web (WWW) uniform
      resource locator (URL).

    o ImageMagick requires an X server for display and animate to work
      properly.  There is a nearly free X server available for Windows
      and Macintosh at

	http://www.microimages.com/freestuf/mix/

    o ImageMagick requires libxml available from

	  http://xmlsoft.org/

      to read the SVG image format.

    o ImageMagick requires the ZLIB library from

	  http://ftp.freesoftware.com/pub/infozip/zlib/

      to read or write the PNG or Zip compressed MIFF images.

    o ImageMagick requires SOCKS version 5 available via the Web at

	  http://www.socks.nec.com/

      in order for 'xtp' to work across a SOCKS5-based firewall. In
      particular, 'xtp' makes use of SOCKS5 'rftp' as an external
      program and supports use of the SOCKS5 library to perform DNS
      lookups via the firewall rather than the internal DNS server.

    o ImageMagick requires a background texture for the TILE
      format and for the -texture option of montage(1).  You can use
      your own or get samples from

          http://the-tech.mit.edu/KPT/


VMS COMPILATION

  You might want to check the values of certain program definitions
  before compiling.  Verify the definitions in delegates.mgk to suit
  your local requirements.  Next, type.

  Type

      unzip ImageMagick-5.2.5.zip set default [.imagemagick] @make set
      display/create/node=node_name::

  where node_name is the DECNET X server to contact.

  Finally type:

      display

  Alternatively, get a zipped distribution (with JPEG, PNG, TIFF, TTF)
  from

      ftp://ftp.wizards.dupont.com/pub/ImageMagick/vms/ImageMagick-5.2.5.zip

  The VMS JPEG, PNG, TIFF, and TTF  source libraries are available on
  axp.psl.ku.dk in [anonymous.decwindows.lib].

  Thanks to pmoreau@cenaath.cena.dgac.fr for supplying invaluable help
  as well as the VMS versions of the JPEG, PNG, TTF, and TIFF
  libraries.


Windows Win2K/95 VISUAL C++ 6.0 COMPILATION

  The Visual C++ distribution targeted at Windows Win2K or Windows 95
  does not provide any stock workspace (DSW) or project files (DSP)
  except for those included with third party libraries. Instead, there
  is a "configure" program that must be built and run that creates an
  environment that meets your particular needs.

  The issue with the Visual C++ working environment is that there are
  a fairly large number of mutually exclusive options that must all be
  used in a coherent manner, or problems result.

  The Visual C++ system provides three different types of "runtimes"
  that must match across all application, library, and DLL code that is
  built. The "configure" program creates a set of build files that are
  consistent for a specific runtime selection.

  The three options for runtime support are:

    1) Dynamic Multi-threaded DLL runtimes.
    2) Static Single-threaded runtimes
    3) Static Multi-threaded runtimes
    4) Static Multi-threaded DLL runtimes

  In addition to these runtimes, the VisualMagick build environment
  allows you to select whether to include the X11 libraries in the
  build or use the X11 "stubs". The assumption is that most Win32 user
  could care less about X11 support, so we stub out all the X11
  functionality so that everything compiles. However, the X11 utility
  programs like display and animage will not work.

  This leads to five different possible build options, which should
  cover almost any particular situation. The default binary
  distribution is built using #1 from above with the X11 libraries
  included. This results in an X11 compatible build using all DLL's for
  everything and multi-threaded support (the only option for DLL's).

  To do a build for your requirements, simply go to the configure sub-
  directory under VisualMagick and open the configure.dsw workspace.
  Set the build configuration to "Release" under the

      "Build..., Set Active Configuration..."  menu.

  Build and execute the configure program and follow the instructions.
  You should probably not change any of the defaults unless you have a
  specific reason to do so.

  After creating your build environment you can proceed to open the DSW
  file that was generated and build everything from there.

  In the final DSW file you will find a project call "All". In order to
  build everything in the distribution, select this project and make it
  the "active" project. Set the build configuration to the desired one
  (Debug, or Release) and do a "clean" followed by a "build". You
  should do the build in a specific way:

    1) Make the "All" project the active project (Bold)
       Right click on the All project and select "Set As Active
       Project"
    2) Select "Build..., Clean"
    3) Select "Build..., Build"
    4) Go get some coffee unless you have a very fast machine!.

  The "Clean" step is needed in order to make sure that all of the
  target support libraries are updated with any patches needed to get
  them to compile properly under Visual C++.

  All of the required files that are needed to run any of the command
  line tools will be found in the "bin" subdirectory of the
  VisualMagick subdirectory. This includes EXE, and DLL files. You
  should be able to test the build directly from this directory without
  having to move anything to any of the global SYSTEM or SYSTEM32 areas
  in the operating system installation.

  NOTE #1:

  The Visual C++ distribution of ImageMagick comes with the Magick++
  C++ wrapper by default. This add-on layer has a large number of demo
  and test files that can be found in ImageMagick\Magick++\demo, and
  ImageMagick\Magick++\tests. There are also a variety of tests that
  use the straight C API as well in ImageMagick\tests.

  All of these programs are NOT configured to be built in the default
  workspace created by the configure program. You can cause all of
  these demos and test programs to be built by checking the box in
  configure that says:

    "Include all demo and test programs"

  In addition, there is another related checkbox (checked by default)
  that causes all generate project files to be created standalone so
  that they can be copied to other areas of you system.

  This is the checkbox:

   "Generate all utility projects with full paths rather then relative
    paths"

  WOW - that a mouthfull - eh?

  The problem is that Visual C++ uses a concept of "dependencies" that
  tell it what other things need to be build when a particular project
  is being build. This mechanism is also used to cause things to link
  properly. In my normal development environment, I want to be able to
  make changes and debug the system as a whole, so I like and NEED to
  use dependencies. However, most end users don't want to work this
  way.

  Instead they really just want to build the package and then get down
  to business working on their application. The solution is to make all
  the utility projects (UTIL_xxxx_yy_exe.dsp) use full absolute paths
  to all the things they need. This way the projects stand on their own
  and can actually be copied and used as templates to get a particular
  custom application compiling with little effort.

  With this feature enabled, you should be able to nab a copy of...
    
    VisualMagick\utilities\UTIL_convert_xxx_exe.dsp  (for C)

     -or-

    VisualMagick\Magick++\demo\UTIL_demo_xxx_exe.dsp (for C++)

  ... and pop it into notepad, modify it (carefully) to your needs and
  be on your way to happy compiling and linking. 

  You can feel free to pick any of the standard utilities, tests, or
  demo programs as the basis for a new program by copying the project
  and the source and hacking away.

  The choice of what to use as a starting point is very easy...

  For straight C API command line applications use something from:

    ImageMagick\tests or ImageMagick\utilities (source code)
    ImageMagick\VisualMagick\tests or ImageMagick\Visualmagick\utilities
      (project - DSP)

  For C++ and Magick++ command line applications use something from:

    ImageMagick\Magick++\tests or ImageMagick\Magick++\demo
      (source code)
    ImageMagick\VisualMagick\Magick++\tests or
      ImageMagick\VisualMagick\Magick++\demo (project - DSP)

  For C++ and Magick++ and MFC windows applications use:
   
    ImageMagick\contrib\win32\MFC\NtMagick (source code)
    ImageMagick\VisualMagick\contrib\win32\MFC\NtMagick
      (project - DSP)

  NOTE #2:

  The 5.2.x distribution is much more modular then any previous release
  of ImageMagick. The default configuration is there to get you
  rolling, but you need to make some serious choices when you wish to
  change things around.

  The binary distribution and default options are all targeted at
  having all the components in one place - the "bin" directory of the
  VisualMagick build tree AND the C:\ImageMagick folder.

  The C:\ImageMagick folder should contain the following files:

      1) magic.mgk
      2) delegates.mgk (derived from nt.mgk)
      3) modules.mgk
      4) rgb.txt

  The "bin" folder should contains all EXE's and DLL's as well as the
  very important "modules.mgk" file.

  With this default setup, you can use any of the command line tools
  and run scripts as normal. You can actually get by quite nicely this
  way by doing something like "pushd e:\xxx\yyy\bin" in any scripts you
  write to execute "out of" this directory.

  ALSO, By default the core of ImageMagick on Win32 always looks in the
  place were the exe program is run from in order to find all of the
  files as well as the DLL's it needs.

  Of course - all of this is configurable and there are certain
  environment variables and compiler switches that allow you to do
  whatever you want. Some of these are Windows things and the rest are
  looked at by the core ImageMagick code.

  ENVIRONMENT VARIABLES:

  You can use the "System" control panel to allow you to add and delete
  what is in any of the environment variables. You can even
  have user specific environment variables if you wish.

  PATH

   This sets the default list of places were Windows looks for EXE's
   and DLL's. Windows CMD shell seems to look in the "current"
   directory first - no matter what, so that is why you really don't
   have to muck. If you wish to run any of utilities from another
   location then you must add the path to your "bin" directory in. For
   instance, you might add:

      D:\CVS\ImageMagick\VisualMagick\bin

   to do this for the default build environment like I do.  One slight
   problem with this is that fact that Windows has another program
   called "convert". I usually rename this to something else since it
   is only used to convert disks from FAT to NTFS.

  MAGICK_HOME

   If all you do is modify the PATH variable, the first problem you
   will run into is that ImageMagick may not be able to find any of its
   "modules. We did not have modules until 5.2 so this is a NEW
   problems. Modules are all the IM_MOD*.DLL files you see in the
   distribution. There is one of these for each and every file format
   that ImageMagick supports. This environment variable tells the
   system were to look for these DLL's. The compiled in "default" is
   "execution path" - which says - look in the same place that the
   application is running "in". If you are running from somewhere other
   then "bin" - this will no longer work and you must use this
   variable. If you elect to leave the modules in the same place as the
   EXE's (a good idea) then you can simply set this to the same place
   as you did the PATH variable. In my case:

      D:\\ImageMagick\coders

   This is also the place were ImageMagick expects to find the all
   important "modules.mgk" file.

   One cool thing about 5.2 is that you can now leave out file formats
   and lighten you load. If all you ever need is GIF and JPEG, then
   simply drop all the other DLL's into the local trash can and get on
   with your life.

   WARNING: Always keep the "xc" format, since IM seems to need and
   "assume" that this one exists and gets real "unhappy" if it does
   not. We are still tracking down some of these issues.

  ALSO. You can elect to changes these things the good old "hard-
  coded" way. Two #defines are applicable.

  defines.h has 

      #define MagickConfigurePath  "c:\\ImageMagick\\"
    #define X11ConfigurePath  "c:\\ImageMagick\\rgb.txt"

  NOTE #3:

  The two utilities "display" and "animate" will only be usable when
  the real X11 libraries are included. The other build environments
  uses the X11 stubs to supply non-functional stubs for the X-Window
  functionality. There is no support for a "static" build of the X11
  support because the build procedures for the X11 libraries do not
  seem to support this.

  To view any image in a Microsoft window, type

      convert image.ext win:

  Make sure gswin32 (Ghostscript) is in your execution path (see
  Autoexec.bat), otherwise, you will be unable to convert or view a
  Postscript document.

  Make sure iexplore (Internet Explorer) is in your execution path (see
  Autoexec.bat), otherwise, you will be unable to browse the
  ImageMagick documentation.

  The Win2K executables will work under Windows 95/98.


MACINTOSH COMPILATION

  The Macintosh distribution contains MetroWerks Codewarrior
  Professional projects for compilation.  For those who do not have
  access to CodeWarrior, the binaries for the command line utilities
  are enclosed.  I had to comment the inline intrinsic functions in
  math.h in order to compile.  If you have a better solution, let me
  know.

  Display(1), animate(1), and import(1) currently do not work on the
  Macintosh.


Magick++

  Magick++ provides a C++ language API to ImageMagick. When configuring
  for Unix, supply the option --with-magick_plus_plus to the configure
  script in order to generate Makefiles which build and install the
  Magick++ headers and library. Magick++ is built by default in the
  Windows build environment. Magick++ is currently supported using the
  egcs 1.1.2 version of GNU g++ (or later) under Unix and Microsoft
  Visual C++ 6.0 under Windows Win2K or Windows 95/98/2000.


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.
