>#ImageMagick: installV<8 

F "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

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

 ImageMagick Studio
 P.O. Box 40
 Landenberg, PA 19350
USA

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

AVAILABILITY

 ImageMagick is available as

e    Jftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-5.4.8.tar.gz


F ImageMagick client executables are available for some platforms. See

U    :ftp://ftp.imagemagick.org/pub/ImageMagick/binaries
P    5ftp://ftp.imagemagick.org/pub/ImageMagick/mac
O    4ftp://ftp.imagemagick.org/pub/ImageMagick/xp
P    5ftp://ftp.imagemagick.org/pub/ImageMagick/vms
R    7ftp://ftp.imagemagick.org/pub/ImageMagick/linux


A I want ImageMagick to be of high quality, so if you encounter aA problem I will investigate. However, be sure you are using the most recent version from

L    1ftp://ftp.imagemagick.org/pub/ImageMagick


; before submitting any bug reports or suggestions. Report6 any problems via the web-based reporting facility at

^    Chttp://studio.imagemagick.org/mailman/listinfo/magick-bugs.


WWW

& The official ImageMagick WWW page is

>    #http://www.imagemagick.org/


? To use display as your external image viewer, edit the globalG 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-user

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

UNIX/Cygwin/MinGW COMPILATION

 Note:

D Platform specific notes regarding specific operating systems mayH be found in the PLATFORMS.txt file. This file (README.txt) providesE generic instructions which work in most common cases. AdditionalG notes regarding Cygwin & MinGW are provided later in this file.

 Type:

1 gzip -dc ImageMagick-5.4.8.tar.gz | tar xvf - cd ImageMagick-5.4.8

@ If you do not have gzip(1), the source for the gzip package is! available as a shell archive at

N    3ftp://ftp.gnu.org/gnu/gzip/gzip-1.2.4a.shar


 or as a tar archive at

M    2ftp://ftp.gnu.org/gnu/gzip/gzip-1.2.4a.tar


@ Use 'configure' to automatically configure, build, and installH ImageMagick. The configure script may be executed from the ImageMagickJ source directory (e.g ./configure) or from a seperate build directory by- specifying the full path to configure (e.g.F /src/ImageMagick-5.4.8/configure). The advantage of using a seperateH build directory is that multiple ImageMagick builds may share the sameH ImageMagick source directory while allowing each build to use a unique set of options.

J If you are willing to accept configure's default options, and build from$ within the source directory, type:

 ./configure

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

= By default, `make install' will install the package's files@ in `/usr/local/bin', `/usr/local/man', etc. You can specify anC installation prefix other than `/usr/local' by giving `configure'F the option `--prefix=PATH'. This is valuable in case you don't haveI privileges to install under the default paths or if you want to install$ in the system directories instead.

G If you are not happy with configure's choice of compiler, compilationB flags, or libraries, you can give `configure' initial values forC variables by specifying them on the configure command line, e.g.:

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

E Options which should be common to packages installed under the sameF directory heirarchy may be supplied via a 'config.site' file locatedH under the installation prefix via the path ${prefix}/share/config.siteH where ${prefix} is the installation prefix. This file is used for allG packages installed under that prefix. This is an example config.site file:

E # Configuration values for all packages installed under this prefix CC=gcc
CXX=c++
% CPPFLAGS='-I/usr/local/include'
- LDFLAGS='-L/usr/local/lib -R/usr/local/lib'

C When the 'config.site' file is being used to supply configuration5 options, configure will issue a message similar to:

? configure: loading site script /usr/local/share/config.site

5 The configure variables you should be aware of are:

;      CC          Name of C compiler (e.g. 'cc -Xa') to use9      CXX         Name of C++ compiler to use (e.g. 'CC')B      CFLAGS      Compiler flags (e.g. '-g -O2') to compile C codeD      CXXFLAGS    Compiler flags (e.g. '-g -O2') to compile C++ codeE      CPPFLAGS    Include paths (-I/somedir) to look for header filesB      LDFLAGS     Library paths (-L/somedir) to look for librariesG                  Systems that support the notion of a library run-pathE                  may require an additional argument in order to findH                  shared libraries at run time. For example, the SolarisG                  linker requires an argument of the form '-R/somedir',F                  some Linux systems will work with '-rpath /somedir',H                  while some other Linux systems who's gcc does not passF                  -rpath to the linker require an argument of the form(                  '-Wl,-rpath,/somedir'.>      LIBS        Extra libraries (-lsomelib) required to link


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

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

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

 Optional Features:


T   --enable-ccmalloc       enable 'ccmalloc' memory debug support (default disabled)M   --enable-prof           enable 'prof' profiling support (default disabled)N   --enable-gprof          enable 'gprof' profiling support (default disabled)M   --enable-gcov           enable 'gcov' profiling support (default disabled)J   --disable-largefile     disable support for large (64 bit) file offsets@   --enable-lzw            enable LZW support (default disabled)


J --disable-16bit-pixel disable 16 bit/quantum pixels (default enabled)

 Optional Packages:


J   --with-modules          enable support for dynamically loadable modulesT   --with-cache            set pixel cache threshhold (defaults to available memory)2   --without-threads       disable threads support


8 --without-frozenpaths disable frozen delegate paths? --without-magick-plus-plus disable build/install of Magick++

>   --without-perl          disable build/install of PerlMagick
        orL   --with-perl=PERL        use specified Perl binary to configure PerlMagickD   --with-perl-options=OPTIONS  options to pass on command-line whenL                           generating PerlMagick's Makefile from Makefile.PL0   --without-bzlib         disable BZLIB support=   --without-dps           disable Display Postscript support3   --without-fpx           disable FlashPIX support>   --without-gslib         disable Ghostscript library support-   --with-hdf              enable HDF support/   --without-jbig          disable JBIG support/   --without-jpeg          disable JPEG support2   --without-jp2           disable JPEG v2 support/   --without-lcms          disable LCMS support/   --without-mpeg2         disable MPEG support.   --without-png           disable PNG support/   --without-tiff          disable TIFF support3   --without-ttf           disable TrueType support.   --without-wmf           disable WMF support>   --with-fontpath         prepend to default font search pathA   --with-gs-font-dir      directory containing Ghostscript fonts@   --with-windows-font-dir directory containing MS-Windows fonts.   --without-xml           disable XML support/   --without-zlib          disable ZLIB support2   --with-x                use the X Window System<   --with-share-path=DIR   Alternate path to share directory6                           (default share/ImageMagick)=   --with-libstdc=DIR      use libstdc++ in DIR (for GNU C++)


H ImageMagick options represent either features to be enabled, disabled,J or packages to be included in the build. When a feature is enabled (viaF --enable-something), it enables code already present in ImageMagick.H When a package is enabled (via --with-something), the configure scriptF will search for it, and if is is properly installed and ready to useI (headers and built libraries are found by compiler) it will be includedD in the build. The configure script is delivered with all featuresC disabled and all packages enabled. In general, the only reason toG disable a package is if a package exists but it is unsuitable for the4 build (perhaps an old version or not compiled with the right compilation flags).

1 Several configure options require special note:


F      ImageMagick built with delegates (see MAGICK PLUG-INS below) canF      pose additional challenges. If ImageMagick is built using staticC      libraries (the default without --enable-shared) then delegateA      libraries may be built as either static libraries or sharedI      libraries. However, if ImageMagick is built using shared libraries,I      then all delegate libraries must also be built as shared libraries.B      Static libraries usually have the extension .a, while sharedI      libraries typically have extensions like .so, .sa, or .dll. Code inF      shared libraries normally must compiled using a special compilerF      option to produce Position Independent Code (PIC). The only timeF      this is not necessary is if the platform compiles code as PIC by      default.B      PIC compilation flags differ from vendor to vendor (gcc's isF      -fPIC). However, you must compile all shared library source withG      the same flag (for gcc use -fPIC rather than -fpic). While staticE      libraries are normally created using an archive tool like 'ar',A      shared libraries are built using special linker or compiler%      options (e.g. -shared for gcc).I      Building shared libraries often requires subtantial hand-editing ofH      Makefiles and is only recommended for those who know what they are      doing.A      If --enable-shared is not specified, a new PERL interpreterB      (PerlMagick) is built which is statically linked against theF      PerlMagick extension. This new interpreter is installed into theE      same directory as the ImageMagick utilities. If --enable-sharedF      is specified, the PerlMagick extension is built as a dynamicallyH      loadable object which is loaded into your current PERL interpreterJ      at run-time. Use of dynamically-loaded extensions is preferable overI      statically linked extensions so --enable-shared should be specifiedE      if possible (note that all libraries used with ImageMagick must      be shared libraries!).


 Building under Cygwin

< ImageMagick may be built under the Windows '95-XP Cygwin6 Unix-emulation environment available for free from

9    http://www.cygwin.com/


& X11R6 for Cygwin is available from

=    "http://xfree86.cygwin.com/


' It is strongly recommended that theC X11R6 package be installed since this enables ImageMagick's X11H support (animate, display, and import will work) and it includes theF Freetype v2 DLL required to support TrueType and Postscript Type 1I fonts. Make sure that /usr/X11R6/bin is in your PATH prior to runningF configure. If you are using Cygwin version 1.3.9 or later, you mayH specify the configure option '--enable-shared' to build Cygwin DLLs.A Specifying '--enable-shared' is required if you want to buildI PerlMagick under Cygwin because Cygwin does not provide the libperl.a: static library required to create a static PerlMagick.

! Building under MinGW & MSYS

H ImageMagick may be built using the free MinGW ("Minimalistic GNU for1 Windows") package version 1.1, available from

7    http://www.mingw.org


E which consists of a GNU-based (e.g. gcc) compilation toolset plusG headers and libraries required to build programs which are entirelyG based on standard Microsoft Windows DLLs. MSYS provides a Unix-likeA console shell window with sufficient functionality to run the2 ImageMagick configure script and execute make.

= Unlike the Cygwin build which creates programs based on aA Unix-emulation DLL, and which uses Unix-style paths to accessA Windows files, the MinGW build creates native Windows console1 applications similar to the Visual C++ build.

G Please note that since the MinGW build is very new, some aspects ofH the installation may vary from Windows user's expectations, and thatD only a static build (no DLLs or modules) is currently supported.

J Once MinGW & MSYS have been installed, start the MSYS console (viaG the MSYS icon on the Windows desktop) and follow the Unix configureH and build instructions. Note that the default installation prefix isE "/usr/local" which installs the package into a MSYS directory. ToB install outside of the MSYS directory tree, you may specify anF installation prefix like "/c/ImageMagick" which causes the packageE to be installed under the Windows directory "C:\ImageMagick". TheF installation directory structure will look very much like the Unix3 installation layout (e.g. "C:\ImageMagick\bin",G "C:\ImageMagick\lib", "C:\ImageMagick\share", etc.). Any additionalF delegate libraries (e.g. libpng) will need to be built under MinGW in order to be used.

& Dealing with configuration failures:

G While configure is designed to ease installation of ImageMagick, itF often discovers problems that would otherwise be encountered laterF when compiling ImageMagick. The configure script tests for headersC and libraries by executing the compiler (CC) with the specifiedJ compilation flags (CFLAGS), pre-processor flags (CPPFLAGS), and linkerG flags (LDFLAGS). Any errors are logged to the file 'config.log'. IfF configure fails to discover a header or library please review thisD log file to determine why, however, please be aware that *errorsC in the config.log are normal* because configure works by tryingF something and seeing if it fails. An error in config.log is only aG problem if the test should have passed on your system. After takingG corrective action, be sure to remove the 'config.cache' file beforeG running configure so that configure will re-inspect the environment$ rather than using cached values.

D Common causes of configure failures are: 1) a delegate header isF not in the header include path (CPPFLAGS -I option); 2) a delegateH library is not in the linker search/run path (LDFLAGS -L/-R option);B 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 maintainerD (currently bfriesen@simple.dallas.tx.us). All bug reports shouldA contain the operating system type (as reported by 'uname -a')E and the compiler/compiler-version. A copy of the configure scriptF output and/or the config.log file may be valuable in order to findG the problem. If you send a config.log, please also send a script ofF the configure output and a description of what you expected to seeD (and why) so the failure you are observing can be identified and resolved.

 Makefile Build Targets

D Once ImageMagick is configured, these standard build targets are+ available from the generated Makefiles:


       'make'          Build the package       'make install'          Install the package       'make check'H          Run tests using the installed ImageMagick ('make install' must          be done first!).       'make clean'D          Remove everything in the build directory created by 'make'       'make distclean'I          Remove everything in the build directory created by 'configure'L          and 'make'. This is useful if you want to start over from scratch.       'make uninstall'@        Remove all files from the system which are (or would be)D        installed by 'make install' using the current configuration.F          Note that this target is imperfect for PerlMagick since Perl3          no longer supports an 'uninstall' target.


 Build & Install:

, Now that ImageMagick is configured, type

make

 to build the package and

 make install

 to install it.

 Verifying The Build:

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

 ./utilities/display

& The ImageMagick logo is displayed.

9 If the image colors are not correct use this command:

+ ./utilities/display -visual default

F For a more serious test, you may run the ImageMagick test suite by typing

 make check

H Note that due to differences between the developer's environment andF your own it is possible that some tests may be indicated as failedG even though the results are ok. Differences between the developer'sF environment environment and your own may include the compiler, theG CPU type, and the library versions used. The ImageMagick developers7 use the current release of all dependent libraries.

 Documentation:

D Be sure to read the manual pages for the display(1), animate(1),E montage(1), import(1), mogrify(1), identify(1), composite(1), andI convert(1) utilities. The ImageMagick(1) manual page provides detailsD for utility options and will also aid with understanding libraryG interfaces. Also read the ImageMagick frequently asked questions in the file www/Magick.html.

 X11 Resources:

. Place display(1) X application defaults inH /usr/lib/X11/app-defaults/Display or in a directory specified by theF XUSERFILESEARCHPATH environment variable. Use the appropriate nameI for other clients (e.g. Animate, Montage, etc). To execute display(1)H from as a menu item of any window manager (olwm, mwm, twm, etc), use

 display logo:Untitled

!MAGICK DELEGATES

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



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


4 to read and write BZip compressed MIFF images.



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


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


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


# to read the Fig image format.



;     http://www.freetype.org/


< to annotate with TrueType and Postscript Type 1 fonts.



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


H      to read the Postscript or the Portable Document format. It is usedG      to annotate an image when the FreeType library is not used, or anC      X server is not available. See the FreeType library above forH      another means to annotate an image. Note, Ghostscript must supportA      the ppmraw device (type gs -h to verify). If Ghostscript isH      unavailable, the Display Postscript extension is used to rasterizeA      a Postscript document (assuming you define HasDPS). The DPSD      extension is less robust than Ghostscript in that it will only2      rasterize one page of a multi-page document.C      Ghostscript (released 7.0 and later) may optionally install aE      library (libgs). If this library is installed, ImageMagick willF      attempt to use it unless the option --without-gslib is passed toH      configure. Note that Ghostscript provides its own modified versionH      of libjpeg and that symbols from this libjpeg may be confused withF      symbols with the stand-alone libjpeg. If conflicts cause JPEG toH      fail, it may be necessary to use Ghostscript's copy of libjpeg forF      ImageMagick, and all delegate libraries which depend on libjpeg.


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


H      to read and write the HDF image format.  By default HDF support is0      disabled because HDF5 is not yet complete.


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


F      to read the HP-GL image format. Note that HPGL is a plotter fileD      format. HP printers usually accept PCL format rather than HPGL
      format.


<    !http://www.littlecms.com/


" to perform color management.



Y    >ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot-3.7.tar.gz


7 to read GNUPLOT plot files (with extension gplt).



I    .http://www.tdb.uu.se/~jan/html2ps.html


$ to read the HTML image format.



J    /http://www.cl.cam.ac.uk/~mgk25/jbigkit/


 or via anonymous FTP as

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


$ to read the JBIG image format.



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


$ to read the JPEG image format.

>      Apply this JPEG patch to Independent JPEG Group's sourceB      distribution if you want to read lossless jpeg-encoded DICOM      (medical) images:f    Kftp://ftp.imagemagick.org/pub/ImageMagick/delegates/ljpeg-6b.tar.gz
K Use of lossless JPEG is not encouraged. Unless you have a requirementM to read lossless jpeg-encoded DICOM images, please disregard the patch.


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


- to read or write the MPEG image format.



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


# to read the PNG image format.



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


( to read the Radiance image format.



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


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



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


/ to import an image from a scanner device.



K    0ftp://ftp.remotesensing.org/pub/libtiff/


 or via HTTP at

:    http://www.libtiff.org/


G      to read the TIFF image format. It in turn optionally requires theI      JPEG and ZLIB libraries. Support for JPEG, ZIP, and LZW compressionG      must be explicitly enabled by editing libtiff Makefiles. The TIFFJ      library no longer includes support for LZW compression due to patentJ      issues. If you need to use LZW compression, support is available viaI      a seperate LZW compression kit (a patch) at the sites listed above.


J    /http://sourceforge.net/projects/wvware/


D      to render files in the Windows Meta File (WMF) metafile formatC      (16-bit WMF files only, not 32-bit "EMF"). This is the formatF      commonly used for Windows clipart (available on CD at your localA      computer or technical book store). WMF support requires theJ      FreeType 2 library in order to render TrueType and Postscript fonts.E      While ImageMagick uses the libwmflite (parser) component of theH      libwmf package which does not depend on any special libraries, theD      libwmf package as a whole depends on FreeType 2 and either theH      xmlsoft libxml, or expat libraries. Since ImageMagick already usesH      libxml (for reading SVG and to retrieve files via HTTP or FTP), itE      is recommended that the options '--without-expat --with-xml' be,      supplied to libwmf's configure script.@      ImageMagick's WMF renderer provides some of the finest WMFH      rendering available due its use of antialiased drawing algorithms.F      You may select a background color or texture image to render on.E      For example, "-background '#ffffffff'" renders on a transparentE      background while "-texture plasma:fractal" renders on a fractal      image.F      A set of Windows 3.1 compatible TrueType fonts (Arial, Times NewC      Roman, and Courier New) may be downloaded without charge from&      Microsoft's web site via the URL[    @http://www.microsoft.com/typography/fontpack/default.htm
H The WMF renderer is not capable of using Windows fonts with libwmfF 0.2.2. Windows fonts are fully supported when using libwmf 0.2.5 or later.


X    =ftp://ftp.imagemagick.org/pub/ImageMagick/delegates/.




= A free X server for Microsoft Windows is available from

G    ,http://sources.redhat.com/win32-x11/


G The Cygwin port of XFree86 may also be used. It is available from

?    $http://www.cygwin.com/xfree/


?      There is a nearly free X server available for Windows and      Macintosh atK    0http://www.microimages.com/freestuf/mix/



6    http://xmlsoft.org/


D      to read the SVG image format and to retrieve files from over a      network via FTP and HTTP.


<    !http://www.gzip.org/zlib/


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



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


VMS COMPILATION

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

 Type

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


4 where node_name is the DECNET X server to contact.

 Finally type:

display

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

f    Kftp://ftp.imagemagick.org/pub/ImageMagick/vms/ImageMagick-5.4.8.zip


F 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

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

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

D The Visual C++ system provides three different types of "runtimes"G that must match across all application, library, and DLL code that isF 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


J In addition to these runtimes, the VisualMagick build environment allowsH you to select whether to include the X11 libraries in the build or useD the X11 "stubs". The assumption is that most Win32 user could careE less about X11 support, so we stub out all the X11 functionality soF that everything compiles. However, the X11 utility programs animate,$ display, and import will not work.

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

O To do a build for your requirements, simply go to the configure subdirectory : under VisualMagick and open the configure.dsw workspace.4 Set the build configuration to "Release" under the

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

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

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

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

    7
  1. Make the "All" project the active project (Bold)H 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!.


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

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

NOTE #1:

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

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

( "Include all demo and test programs"

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

 This is the checkbox:

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

 WOW - that a mouthfull - eh?

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

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

C 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++)

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

D You can feel free to pick any of the standard utilities, tests, orE 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...

B For straight C API command line applications use something from:

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

D 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)

8 For C++ and Magick++ and MFC windows applications use:

8 ImageMagick\contrib\win32\MFC\NtMagick (source code)7 ImageMagick\VisualMagick\contrib\win32\MFC\NtMagick (project - DSP)

NOTE #2:

; The ImageMagick distribution is very modular. The defaultF configuration is there to get you rolling, but you need to make some8 serious choices when you wish to change things around.

A The binary distribution and default options are all targeted atE having all the components in one place - the "bin" directory of the8 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


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

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

G ALSO, By default the core of ImageMagick on Win32 always looks in theD 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 certainB environment variables and compiler switches that allow you to doF whatever you want. Some of these are Windows things and the rest are) looked at by the core ImageMagick code.

'ENVIRONMENT VARIABLES:

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

PATH

H This sets the default list of places were Windows looks for EXE's andJ DLL's. Windows CMD shell seems to look in the "current" directory first



) D:\CVS\ImageMagick\VisualMagick\bin

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

MAGICK_HOME

C If all you do is modify the PATH variable, the first problem youC will run into is that ImageMagick may not be able to find any ofE its "modules. Modules are all the IM_MOD*.DLL files you see in theE distribution. There is one of these for each and every file formatH that ImageMagick supports. This environment variable tells the systemH were to look for these DLL's. The compiled in "default" is "executionF path" - which says - look in the same place that the application isE running "in". If you are running from somewhere other then "bin" -H this will no longer work and you must use this variable. If you electD to leave the modules in the same place as the EXE's (a good idea)1 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 theA "colors.mgk", "delegates.mgk", "magic.mgk", "modules.mgk", and "type.mgk" files.

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

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

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

 defines.h has

6 #define MagickConfigurePath "c:\\ImageMagick\\"

NOTE #3:

D The two utilities "display" and "animate" will only be usable whenC the real X11 libraries are included. The other build environmentsD uses the X11 stubs to supply non-functional stubs for the X-WindowD functionality. There is no support for a "static" build of the X11H 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 (seeC Autoexec.bat), otherwise, you will be unable to convert or view a Postscript document.

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

6 The Win2K executables will work under Windows 95/98.

&MACINTOSH COMPILATION

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

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

Magick++

F Magick++ provides a straightforward C++ language API to ImageMagick.E Magick++ is built by default under the Unix, Windows, and Mac build@ environments. To disable building Magick++ under Unix, specifyD --without-magick-plus-plus as an argument to the configure script.

D Magick++ is currently supported using the following C++ compilers:

 egcs 1.1.2 (or later)
 gcc 2.95.2 (or later)
Visual C++ 6.0 (Windows)
 IRIX C++ 7.3.1.1m
 HP-UX HP-UX aCC A.03.30
C Sun Workshop 5.0 C++ (tests/demos require work-around to build) Sun Forte 6.0 C++
2 CodeWarrior Professional Release 5 (Macintosh)

; and may compile under other modern C++ compilers as well.




>

9Image manipulation software that works like magic.