ImageMagick Advanced Unix Installation
It's possible you don't want to concern yourself with advanced installation under Unix or Linux systems. If so, you also have the option of installing a pre-compiled binary release or if you still want to install from source without all the fuss see the simple Install From Source instructions. However, if you want to customize the configuration and installation of ImageMagick under Unix or Linux systems, lets begin.
Download & Unpack
+Download & Unpack
ImageMagick builds on a variety of Unix and Unix-like operating systems including Linux, Solaris, FreeBSD, Mac OS X, and others. A compiler is required and fortunately almost all modern Unix systems have one. Download ImageMagick.tar.gz from ftp.imagemagick.org or its mirrors and verify the distribution against its message digest.
@@ -189,17 +219,16 @@Configure
+Configure
The configure script looks at your environment and decides what it can cobble together to get ImageMagick compiled and installed on your system. This includes finding a compiler, where your compiler header files are located (e.g. stdlib.h), and if any delegate libraries are available for ImageMagick to use (e.g. JPEG, PNG, TIFF, etc.). If you are willing to accept configure's default options, and build from within the source directory, you can simply type:
-$magick> cd ImageMagick-6.6.5-4 $magick> ./configure
+$magick> cd ImageMagick-6.7.0-1 $magick> ./configure
Watch the configure script output to verify that it finds everything that you think it should. Pay particular attention to the last lines of the script output. For example, here is a recent report from our system:
You can influence choice of compiler, compilation flags, or libraries of the configure script by setting initial values for variables in the configure command line. These include, among others:
@@ -418,6 +446,8 @@ Options used to compile and link: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 passed on your system.
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?); or 4) compilation environment is faulty.
-If all reasonable corrective actions have been tried and the problem appears be due to a flaw in the configure script, please send a bug report to the ImageMagick Defect Support Forum. 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 relevant portion of config.log file may be valuable in order to find the problem. If you post portions of 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.
+If all reasonable corrective actions have been tried and the problem appears be due to a flaw in the configure script, please send a bug report to the ImageMagick Defect Support Forum. 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 relevant portion of config.log file may be valuable in order to find the problem. If you post portions of 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.
ImageMagick is now configured and ready to build
Build
+Build
Once ImageMagick is configured, these standard build targets are available from the generated make files:
@@ -484,7 +514,7 @@ Options used to compile and link:Once built, you can optionally install ImageMagick on your system as discussed below.
Install
+Install
Now that ImageMagick is configured and built, type:
@@ -512,7 +542,7 @@ Options used to compile and link:Linux-specific Build instructions
+Linux-specific Build instructions
Download ImageMagick.src.rpm from ftp.imagemagick.org or its mirrors and verify the distribution against its message digest.
@@ -522,10 +552,10 @@ Options used to compile and link:$magick> rpmbuild --rebuild ImageMagick.src.rpm
After the build you, locate the RPMS folder and install the ImageMagick binary RPM distribution:
-$magick> rpm -ivh ImageMagick-6.6.5-?.*.rpm
+$magick> rpm -ivh ImageMagick-6.7.0-?.*.rpm
Mac OS X-specific Build instructions
+Mac OS X-specific Build instructions
Perform these steps as an administrator or with the sudo command:
@@ -546,7 +576,7 @@ Options used to compile and link:Download the ImageMagick source distribution and verify the distribution against its message digest.
Unpack and change into the top-level ImageMagick directory:
-$magick> tar xvfz ImageMagick-6.6.5-4.tar.gz $magick> cd ImageMagick-6.6.5-4
Configure ImageMagick:
+$magick> tar xvfz ImageMagick-6.7.0-1.tar.gz $magick> cd ImageMagick-6.7.0-1
Configure ImageMagick:
$magick> ./configure --prefix=/opt --with-quantum-depth=16 \
--disable-dependency-tracking --with-x=yes \
--x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib/ \
@@ -561,14 +591,14 @@ Options used to compile and link:
MinGW-specific Build instructions
+MinGW-specific Build instructions
Although you can download and install delegate libraries yourself, many are already available in the GnuWin32 distribution. Download and install whichever delegate libraries you require such as JPEG, PNG, TIFF, etc. Make sure you specify the development headers when you install a package. Next type,
-$magick> tar jxvf ImageMagick-6.6.5-?.tar.bz2 $magick> cd ImageMagick-6.6.5-4 $magick> export CPPFLAGS="-Ic:/Progra~1/GnuWin32/include" $magick> export LDFLAGS="-Lc:/Progra~1/GnuWin32/lib" $magick> ./configure --without-perl $magick> make $magick> sudo make install
$magick> tar jxvf ImageMagick-6.7.0-?.tar.bz2 $magick> cd ImageMagick-6.7.0-1 $magick> export CPPFLAGS="-Ic:/Progra~1/GnuWin32/include" $magick> export LDFLAGS="-Lc:/Progra~1/GnuWin32/lib" $magick> ./configure --without-perl $magick> make $magick> sudo make install
Dealing with Unexpected Problems
+Dealing with Unexpected Problems
Chances are the download, configure, build, and install of ImageMagick went flawlessly as it is intended, however, certain systems and environments may cause one or more steps to fail. We discuss a few problems we've run across and how to take corrective action to ensure you have a working release of ImageMagick
@@ -616,7 +646,7 @@ Options used to compile and link: