Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / ImageMagick / 5292344af862c8d10e50c4e9300a591aad3acae5 / . / www / advanced-unix-installation.html
blob: 08409621e7667d4655ea5a866e05d66284ae4206 [file] [log] [blame]
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" dir="ltr">
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]4<head>
cristy3c98a4f2010-08-13 20:09:41 +0000[diff] [blame]5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
6 <meta name="verify-v1" content="g222frIIxcQTrvDR3NBRUSKP3AnMNoqxOkIniCEkV7U="/>
cristyffb69ed2010-12-25 00:06:48 +0000[diff] [blame]7 <title>ImageMagick: Advanced Unix Source Installation</title>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]8 <meta http-equiv="Content-Language" content="en-US"/>
9 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
10 <meta http-equiv="Reply-to" content="magick-users@imagemagick.org"/>
cristy3c98a4f2010-08-13 20:09:41 +0000[diff] [blame]11 <meta name="Application-name" content="ImageMagick"/>
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]12 <meta name="Description" content="ImageMagick is a software suite to create, edit, compose, or convert bitmap images in a variety of formats. Use ImageMagick to scale, rotate, shear, distort and transform images."/>
cristy3c98a4f2010-08-13 20:09:41 +0000[diff] [blame]13 <meta name="Application-url" content="http://www.imagemagick.org"/>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]14 <meta name="Generator" content="PHP"/>
15 <meta name="Keywords" content="advanced, unix, source, installation, ImageMagick, ImageMagic, MagickCore, MagickWand, PerlMagick, Magick++, RMagick, PythonMagick, JMagick, TclMagick, Image, Magick, Magic, Wand, ImageMagickObject, Swiss, Army, Knife, Image, Processing"/>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]16 <meta name="Rating" content="GENERAL"/>
17 <meta name="Robots" content="INDEX, FOLLOW"/>
18 <meta name="Generator" content="ImageMagick Studio LLC"/>
19 <meta name="Author" content="ImageMagick Studio LLC"/>
20 <meta name="Revisit-after" content="2 DAYS"/>
21 <meta name="Resource-type" content="document"/>
cristy7e41fe82010-12-04 23:12:08 +0000[diff] [blame]22 <meta name="Copyright" content="Copyright (c) 1999-2011 ImageMagick Studio LLC"/>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]23 <meta name="Distribution" content="Global"/>
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]24 <link rel="icon" href="../images/wand.png"/>
cristy3c98a4f2010-08-13 20:09:41 +0000[diff] [blame]25 <link rel="shortcut icon" href="../images/wand.ico" type="images/x-icon"/>
26 <link rel="meta" type="application/rdf+xml" title="ICI" href="http://imagemagick.org/ici.rdf"/>
cristy7a40ba82011-01-08 20:31:18 +0000[diff] [blame]27 <link rel="stylesheet" href="http://www.google.com/cse/style/look/default.css" type="text/css" />
cristy3c98a4f2010-08-13 20:09:41 +0000[diff] [blame]28 <style type="text/css" media="all">
29 @import url("../www/magick.css");
30 </style>
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]31 <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4/jquery.min.js"></script>
cristy361f4662010-12-31 23:02:52 +0000[diff] [blame]32 <script type="text/javascript" src="../fancybox/jquery.fancybox-1.3.4.pack.js"></script>
33 <link rel="stylesheet" type="text/css" href="../fancybox/jquery.fancybox-1.3.4.css" media="screen" />
34 <script type="text/javascript">
35 $(document).ready(function() {
36 $("a[href$=.jpg],a[href$=.png],a[href$=.gif]").fancybox({
37 'transitionIn' : 'elastic',
38 'transitionOut' : 'elastic',
39 'overlayShow' : false,
40 'opacity' : true
41 });
42 });
43 </script>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]44</head>
45
46<body id="www-imagemagick-org">
47<div class="titlebar">
48<a href="../index.html">
49 <img src="../images/script.png" alt="[ImageMagick]"
50 style="width: 350px; height: 60px; margin: 28px auto; float: left;" /></a>
51<a href="http://www.networkredux.com">
52 <img src="../images/networkredux.png" alt="[sponsor]"
cristy52923442011-01-15 22:54:31 +0000[diff] [blame^]53 style="margin-top: 42px; border: 0px; float: left;" /></a>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]54<a href="http://www.imagemagick.org/discourse-server/">
55 <img src="../images/logo.jpg" alt=""
56 style="width: 114px; height: 118px; border: 0px; float: right;" /></a>
57<a href="../index.html">
58 <img src="../images/sprite.jpg" alt=""
59 style="width: 114px; height: 118px; border: 0px; float: right;" /></a>
60</div>
61
cristyce69bb02010-07-27 19:49:46 +0000[diff] [blame]62<div class="westbar">
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]63
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]64<div class="menu">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]65 <a title="About ImageMagick" href="../index.html">About ImageMagick</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]66</div>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]67<div class="sep"></div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]68<div class="menu">
cristybb503372010-05-27 20:51:26 +0000[diff] [blame]69 <a title="Binary Releases" href="../www/binary-releases.html">Binary Releases</a>
70</div>
71<div class="sub">
72 <a title="Binary Release: Unix" href="../www/binary-releases.html#unix">Unix</a>
73</div>
74<div class="sub">
75 <a title="Binary Release: MacOS X" href="../www/binary-releases.html#macosx">Mac OS X</a>
76</div>
77<div class="sub">
78 <a title="Binary Release: Windows" href="../www/binary-releases.html#windows">Windows</a>
79</div>
80<div class="sep"></div>
81<div class="menu">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]82 <a title="Command-line Tools" href="../www/command-line-tools.html">Command-line Tools</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]83</div>
84<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]85 <a title="Command-line Tools: Processing" href="../www/command-line-processing.html">Processing</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]86</div>
87<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]88 <a title="Command-line Tools: Options" href="../www/command-line-options.html">Options</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]89</div>
90<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]91 <a title="Command-line Tools: Usage" href="http://www.imagemagick.org/Usage/">Usage</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]92</div>
93<div class="menu">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]94 <a title="Program Interfaces" href="../www/api.html">Program Interfaces</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]95</div>
96<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]97 <a title="Program Interface: MagickWand" href="../www/magick-wand.html">MagickWand</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]98</div>
99<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]100 <a title="Program Interface: MagickCore" href="../www/magick-core.html">MagickCore</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]101</div>
102<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]103 <a title="Program Interface: PerlMagick" href="../www/perl-magick.html">PerlMagick</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]104</div>
105<div class="sub">
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]106 <a title="Program Interface: Magick++" href="../www/magick++.html">Magick++</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]107</div>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]108<div class="sep"></div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]109<div class="menu">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]110 <a title="Install from Source" href="../www/install-source.html">Install from Source</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]111</div>
112<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]113 <a title="Install from Source: Unix" href="../www/install-source.html#unix">Unix</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]114</div>
115<div class="sub">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]116 <a title="Install from Source: Windows" href="../www/install-source.html#windows">Windows</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]117 </div>
118<div class="menu">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]119 <a title="Resources" href="../www/resources.html">Resources</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]120</div>
cristybb503372010-05-27 20:51:26 +0000[diff] [blame]121<div class="menu">
122 <a title="Architecture" href="../www/architecture.html">Architecture</a>
123</div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]124<div class="menu">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]125 <a title="Download" href="../www/download.html">Download</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]126</div>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]127<div class="sep"></div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]128<div class="menu">
cristy52923442011-01-15 22:54:31 +0000[diff] [blame^]129 <a title="Search" href="../www/search.html">Search</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]130</div>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]131<div class="sep"></div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]132<div class="menu">
cristyffb69ed2010-12-25 00:06:48 +0000[diff] [blame]133 <a title="Site Map" href="../www/sitemap.html">Site Map</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]134</div>
135<div class="sub">
cristyffb69ed2010-12-25 00:06:48 +0000[diff] [blame]136 <a title="Site Map: Links" href="../www/links.html">Links</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]137</div>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]138<div class="sep"></div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]139<div class="menu">
cristy83a272e2010-05-07 20:40:35 +0000[diff] [blame]140 <a title="Sponsors" href="../www/sponsors.html">Sponsors:</a>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]141
142<div class="sponsbox">
cristyec6b4752011-01-08 03:16:23 +0000[diff] [blame]143<div class="sponsor">
cristy52923442011-01-15 22:54:31 +0000[diff] [blame^]144 <a title="Sponsor: Web Hosting" href="http://www.bodhost.com/hosting.shtml">Web Hosting</a><!-- 201104010090 -->
cristy73fd1cd2010-09-12 19:14:25 +0000[diff] [blame]145</div>
146<div class="sponsor">
cristy7d52cd62010-10-01 17:26:59 +0000[diff] [blame]147 <a title="Sponsor: Druckerei" href="http://print24.com/de/">Druckerei</a><!-- 201110010720 -->
148</div>
149<div class="sponsor">
cristyc5baf4f2010-08-31 15:05:33 +0000[diff] [blame]150 <a title="Sponsor: Image Converter" href="http://www.batchphoto.com">Image Converter</a><!-- 201103010900 Bits Coffee-->
151</div>
152<div class="sponsor">
cristy851dbce2010-08-06 21:40:00 +0000[diff] [blame]153 <a title="Sponsor: Flyer drucken" href="http://www.online-druck.biz">Flyer drucken</a><!-- 201109010900 Floeter-->
154</div>
cristyec6b4752011-01-08 03:16:23 +0000[diff] [blame]155<div class="sponsor">
cristy52923442011-01-15 22:54:31 +0000[diff] [blame^]156 <a title="Sponsor: Notebook Reparatur Berlin" href="http://www.notebook-reparaturen-berlin.de">Notebook Reparatur Berlin</a><!-- 2011050100025 gabi.schulze-->
cristyec6b4752011-01-08 03:16:23 +0000[diff] [blame]157</div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]158</div>
159</div>
cristyce69bb02010-07-27 19:49:46 +0000[diff] [blame]160</div>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]161
cristyce69bb02010-07-27 19:49:46 +0000[diff] [blame]162<div class="eastbar">
163 <script type="text/javascript">
164 <!--
165 google_ad_client = "pub-3129977114552745";
cristyce69bb02010-07-27 19:49:46 +0000[diff] [blame]166 google_ad_slot = "0574824969";
167 google_ad_width = 160;
168 google_ad_height = 600;
169 //-->
170 </script>
171 <script type="text/javascript"
172 src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
173 </script>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]174</div>
175
176<div class="main">
177
178
cristyffb69ed2010-12-25 00:06:48 +0000[diff] [blame]179<h1>ImageMagick Advanced Unix Installation</h1>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]180<p class="navigation-index">[<a href="#download">Download &amp; Unpack</a> &bull; <a href="#configure">Configure</a> &bull; <a href="#build">Build</a> &bull; <a href="#install">Install</a> &bull; <a href="#linux">Linux-specific Build Instructions</a> &bull; <a href="#macosx">Mac OS X-specific Build Instructions</a> &bull; <a href="#mingw">MinGW-specific Build Instructions</a> &bull; <a href="#problems">Dealing with Unexpected Problems</a>]</p>
181
182<div class="doc-section">
183<p>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 <a href="../www/binary-releases.html#unix">binary release</a> or if you still want to install from source without all the fuss see the simple <a href="../www/install-source.html#unix">Install From Source</a> instructions. However, if you want to customize the configuration and installation of ImageMagick under Unix or Linux systems, lets begin.</p>
184</div>
185
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]186<h2><a id="download"></a>Download &amp; Unpack</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]187<div class="doc-section">
188
189<p>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 <a href="ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick.tar.gz">ImageMagick.tar.gz</a> from <a href="ftp://ftp.imagemagick.org/pub/ImageMagick">ftp.imagemagick.org</a> or its <a href="../www/download.html">mirrors</a> and verify the distribution against its <a href="http://www.imagemagick.org/download/digest.rdf">message digest</a>.</p>
190
191<p>Unpack the distribution it with this command:</p>
192
193<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>tar xvfz ImageMagick.tar.gz</span></p>
194<p>Now that you have the ImageMagick Unix/Linux source distribution unpacked, let's configure it.</p>
195
196</div>
197
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]198<h2><a id="configure"></a>Configure</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]199<div class="doc-section">
200
201<p>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:</p>
202
cristyec6b4752011-01-08 03:16:23 +0000[diff] [blame]203<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>cd ImageMagick-6.6.7-0</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>./configure</span></p>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]204<p>Watch the configure script output to verify that it finds everything that
205 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:</p>
206
207<div class="viewport">
208<pre class="text">
209ImageMagick is configured as follows. Please verify that this configuration
210matches your expectations.
211
212Host system type: x86_64-unknown-linux-gnu
213Build system type: x86_64-unknown-linux-gnu
214
215 Option Value
216-------------------------------------------------------------------------------
217Shared libraries --enable-shared=yes yes
218Static libraries --enable-static=yes yes
219Module support --with-modules=yes yes
220GNU ld --with-gnu-ld=yes yes
221Quantum depth --with-quantum-depth=16 16
222High Dynamic Range Imagery
223 --enable-hdri=no no
224
225Delegate Configuration:
226BZLIB --with-bzlib=yes yes
227Autotrace --with-autotrace=yes yes
228DJVU --with-djvu=yes no
229DPS --with-dps=yes no
230FlashPIX --with-fpx=yes no
231FontConfig --with-fontconfig=yes yes
232FreeType --with-freetype=yes yes
233GhostPCL None pcl6 (unknown)
234GhostXPS None gxps (unknown)
235Ghostscript None gs (8.63)
236result_ghostscript_font_dir='none'
237Ghostscript fonts --with-gs-font-dir=default
238Ghostscript lib --with-gslib=yes no (failed tests)
239Graphviz --with-gvc=yes yes
240JBIG --with-jbig= no
241JPEG v1 --with-jpeg=yes yes
242JPEG-2000 --with-jp2=yes yes
243LCMS --with-lcms=yes yes
244LQR --with-lqr=yes no
245Magick++ --with-magick-plus-plus=yes yes
246OpenEXR --with-openexr=yes yes
247PERL --with-perl=yes /usr/bin/perl
248PNG --with-png=yes yes
249RSVG --with-rsvg=yes yes
250TIFF --with-tiff=yes yes
251result_windows_font_dir='none'
252Windows fonts --with-windows-font-dir=
253WMF --with-wmf=yes yes
254X11 --with-x= yes
255XML --with-xml=yes yes
256ZLIB --with-zlib=yes yes
257
258X11 Configuration:
259 X_CFLAGS =
260 X_PRE_LIBS = -lSM -lICE
261 X_LIBS =
262 X_EXTRA_LIBS =
263
264Options used to compile and link:
265 PREFIX = /usr/local
266 EXEC-PREFIX = /usr/local
267 VERSION = 6.4.8
268 CC = gcc -std=gnu99
269 CFLAGS = -fopenmp -g -O2 -Wall -W -pthread
270 MAGICK_CFLAGS = -fopenmp -g -O2 -Wall -W -pthread
271 CPPFLAGS = -I/usr/local/include/ImageMagick
272 PCFLAGS = -fopenmp
273 DEFS = -DHAVE_CONFIG_H
274 LDFLAGS = -lfreetype
275 MAGICK_LDFLAGS = -L/usr/local/lib -lfreetype
276 LIBS = -lMagickCore -llcms -ltiff -lfreetype -ljpeg -lfontconfig -lXext
277 -lSM -lICE -lX11 -lXt -lbz2 -lz -lm -lgomp -lpthread -lltdl
278 CXX = g++
279 CXXFLAGS = -g -O2 -Wall -W -pthread
280</pre>
281</div>
282
283<p>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:</p>
284
285<dl class="doc">
286<dt>CC</dt>
287 <dd>Name of C compiler (e.g. <kbd>cc -Xa</kbd>) to use.</dd>
288<dt>CXX</dt>
289 <dd>Name of C++ compiler to use (e.g. <kbd>CC</kbd>).</dd>
290<dt>CFLAGS</dt>
291 <dd>Compiler flags (e.g. <kbd>-g -O2</kbd>) to compile C code.</dd>
292<dt>CXXFLAGS</dt>
293 <dd>Compiler flags (e.g. <kbd>-g -O2</kbd>) to compile C++ code.</dd>
294<dt>CPPFLAGS</dt>
295 <dd>Include paths (.e.g. <kbd>-I/usr/local</kbd>) to look for header files.</dd>
296<dt>LDFLAGS</dt>
297 <dd>Library paths (.e.g. <kbd>-L/usr/local</kbd>) to look for libraries systems that support the notion of a library run-path may require an additional argument in order to find shared libraries at run time. For example, the Solaris linker requires an argument of the form <em>-R/path</em>. Some Linux systems will work with <kbd>-rpath /usr/local/lib</kbd>, while some other Linux systems who's gcc does not pass <kbd>-rpath</kbd> to the linker, require an argument of the form <kbd>-Wl,-rpath,/usr/local/lib</kbd>.</dd>
298<dt>LIBS</dt>
299 <dd>Extra libraries (.e.g. <kbd>-l/usr/local/lib</kbd>) required to link.</dd>
300</dl>
301
302<p>Here is an example of setting configure variables from the command line:</p>
303
cristy6242f6a2010-02-18 02:20:56 +0000[diff] [blame]304<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>./configure CC=c99 CFLAGS=-O2 LDFLAGS='-L/usr/local/lib -R/usr/local/lib' LIBS=-lposix</span></p>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]305<p>Any variable (e.g. CPPFLAGS or LDFLAGS) which requires a directory path must specify an absolute path rather than a relative path.</p>
306
307<p>Configure can usually find the X include and library files automagically, but if it doesn't, you can use the <em>--x-includes=path</em> and <em>--x-libraries=path</em> options to specify their locations.</p>
308
309<p>The configure script provides a number of ImageMagick specific options. When disabling an option <em>--disable-something</em> is equivalent to specifying <em>--enable-something=no</em> and <em>--without-something</em> is equivalent to <em>--with-something=no</em>. The configure options are as follows (execute <kbd>configure --help</kbd> to see all options).</p>
310
311<p> ImageMagick options represent either features to be enabled, disabled, or packages to be included in the build. When a feature is enabled (via <em>--enable-something</em>), it enables code already present in ImageMagick. When a package is enabled (via <em>--with-something</em>), the configure script will search for it, and if 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).</p>
312
313<p>Here are the optional features you can configure:</p>
314
315<dl class="doc">
316<dt>--enable-shared</dt>
317 <dd>build the shared libraries and support for loading coder and process modules. Shared libraries are preferred because they allow programs to share common code, making the individual programs much smaller. In addition shared libraries are required in order for PerlMagick to be dynamically loaded by an installed PERL (otherwise an additional PERL (PerlMagick) must be installed.
318 <br /><br />
319 ImageMagick built with delegates (see MAGICK PLUG-INS below) can pose additional challenges. If ImageMagick is built using static libraries (the default without <kbd>--enable-shared</kbd>) then delegate libraries may be built as either static libraries or shared libraries. However, if ImageMagick is built using shared libraries, then all delegate libraries must also be built as shared libraries. Static libraries usually have the extension <kbd>.a</kbd>, while shared libraries typically have extensions like <kbd>.so</kbd>, <kbd>.sa</kbd>, or <kbd>.dll</kbd>. Code in shared libraries normally must compiled using a special compiler option to produce Position Independent Code (PIC). The only time this not necessary is if the platform compiles code as PIC by default.
320 <br /><br />
321 PIC compilation flags differ from vendor to vendor (gcc's is <kbd>-fPIC</kbd>). However, you must compile all shared library source with the same flag (for gcc use <kbd>-fPIC</kbd> rather than <kbd>-fpic</kbd>). While static libraries are normally created using an archive tool like <kbd>ar</kbd>, shared libraries are built using special linker or compiler options (e.g. <kbd>-shared</kbd> for gcc).
322 <br/><br />
323 If <kbd>--enable-shared</kbd> is not specified, a new PERL interpreter (PerlMagick) is built which is statically linked against the PerlMagick extension. This new interpreter is installed into the same directory as the ImageMagick utilities. If <kbd>--enable-shared</kbd> 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 use <kbd>--enable-shared</kbd> if possible (note that all libraries used with ImageMagick must be shared libraries!).</dd>
324<dt>--disable-static</dt>
325 <dd>static archive libraries (with extension <kbd>.a</kbd>) 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) 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.</dd>
326<dt>--disable-installed</dt>
327 <dd>disable building an installed ImageMagick (default enabled).
328 <br/><br />
329 By default the ImageMagick build is configured to formally install into a directory tree. This the most secure and reliable way to install ImageMagick. Use this option to configure ImageMagick so that it doesn't use hard-coded paths and locates support files by computing an offset path from the executable (or from the location specified by the MAGICK_HOME environment variable. The uninstalled configuration is ideal for binary distributions which are expected to extract and run in any location.</dd>
330<dt>--enable-ccmalloc</dt>
331 <dd>enable 'ccmalloc' memory debug support (default disabled).</dd>
332<dt>--enable-prof</dt>
333 <dd>enable 'prof' profiling support (default disabled).</dd>
334<dt>--enable-gprof</dt>
335 <dd>enable 'gprof' profiling support (default disabled).</dd>
336<dt>--enable-gcov</dt>
337 <dd>enable 'gcov' profiling support (default disabled).</dd>
338<dt>--disable-openmp</dt>
339 <dd>disable OpenMP (default enabled).
340 <br/><br />
341 Certain ImageMagick algorithms, for example convolution, can achieve a significant speed-up with the assistance of the OpenMP API when running on modern dual and quad-core processors.</dd>
342<dt>--disable-largefile</dt>
343 <dd>disable support for large (64 bit) file offsets.
344 <br/><br />
345 By default, ImageMagick is compiled with support for large files (&gt; 2GB on a 32-bit CPU) if the operating system supports large files. Some applications which use the ImageMagick library may also require support for large files. By disabling support for large files via <kbd>--disable-largefile</kbd>, dependent applications do not require special compilation options for large files in order to use the library.</dd>
346</dl>
347
348<p>Here are the optional packages you can configure:</p>
349
350<dl class="doc">
351<dt>--with-quantum-depth</dt>
352 <dd>number of bits in a pixel quantum (default 16).
353 <br/><br />
354 Use this option to specify the number of bits to use per pixel quantum (the size of the red, green, blue, and alpha pixel components). For example, <kbd>--with-quantum-depth=8</kbd> builds ImageMagick using 8-bit quantums. Most computer display adapters use 8-bit quantums. Currently supported arguments are 8, 16, or 32. We recommend the default of 16 because some image formats support 16 bits-per-pixel. However, this option is important in determining the overall run-time performance of ImageMagick.
355 <br /><br />
356 The number of bits in a quantum determines how many values it may contain. Each quantum level supports 256 times as many values as the previous level. The following table shows the range available for various quantum sizes.
357 <br /><br />
358 <pre class="text">
cristyf0d1f5d2010-05-13 16:29:38 +0000[diff] [blame]359 Quantum Depth Valid Range (Decimal) Valid Range (Hex)
360 8 0-255 00-FF
361 16 0-65535 0000-FFFF
362 32 0-4294967295 00000000-FFFFFFFF
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]363 </pre>
364 <br /><br />
365 Larger pixel quantums can cause ImageMagick to run more slowly and to require more memory. For example, using sixteen-bit pixel quantums can cause ImageMagick to run 15% to 50% slower (and take twice as much memory) than when it is built to support eight-bit pixel quantums.
366 <br /><br />
367 The amount of virtual memory consumed by an image can be computed by the equation <em>(5 * Quantum Depth * Rows * Columns) / 8</em>. This an important consideration when resources are limited, particularly since processing an image may require several images to be in memory at one time. The following table shows memory consumption values for a 1024x768 image:
368 <br /><br />
369 <pre class="text">
370 Quantum Depth Virtual Memory
371 8 3MB
372 16 8MB
373 32 15MB
374 </pre></dd>
375 <dt>--enable-hdri</dt>
cristyd0bda5e2010-09-21 16:22:45 +0000[diff] [blame]376 <dd>accurately represent the wide range of intensity levels.</dd>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]377 <dt>--enable-osx-universal-binary</dt>
378 <dd>build a universal binary on OS X.</dd>
379 <dt>--without-modules</dt>
380 <dd>disable support for dynamically loadable modules.
381 <br /><br />
382 Image coders and process modules are built as loadable modules which are installed under the directory <em>[prefix]/lib/ImageMagick-X.X.X/modules-QN</em> (where 'N' equals 8, 16, or 32 depending on the quantum depth) in the subdirectories <kbd>coders</kbd> and <kbd>filters</kbd> respectively. The modules build option is only available in conjunction with <kbd>--enable-shared</kbd>. If <kbd>--enable-shared</kbd> is not also specified, support for building modules is disabled. Note that if <kbd>--enable-shared</kbd> and <kbd>--disable-modules</kbd> are specified, the module loader is active (allowing extending an installed ImageMagick by simply copying a module into place) but ImageMagick itself is not built using modules.</dd>
383<dt>--with-cache</dt>
384 <dd>set pixel cache threshold (defaults to available memory).
385 <br /><br />
386 Specify a different image pixel cache threshold with this option. This sets the maximum amount of heap memory that ImageMagick is allowed to consume before switching to using memory-mapped temporary files to store raw pixel data.</dd>
387<dt>--without-threads</dt>
388 <dd>disable threads support.
389 <br /><br />
390 By default, the ImageMagick library is compiled with multi-thread support. If this undesirable, specify <kbd>--without-threads</kbd>.</dd>
391<dt>--with-frozenpaths</dt>
392 <dd>enable frozen delegate paths.
393 <br /><br />
394 Normally, external program names are substituted into the <kbd>delegates.xml</kbd> configuration file without full paths. Specify this option to enable saving full paths to programs using locations determined by configure. This useful for environments where programs are stored under multiple paths, and users may use different PATH settings than the person who builds ImageMagick.</dd>
395<dt>--without-magick-plus-plus</dt>
396 <dd>disable build/install of Magick++.
397 <br /><br />
398 Disable building Magick++, the C++ application programming interface to ImageMagick. A suitable C++ compiler is required in order to build Magick++. Specify the CXX configure variable to select the C++ compiler to use (default <kbd>g++</kbd>), and CXXFLAGS to select the desired compiler optimization and debug flags (default <kbd>-g -O2</kbd>). Antique C++ compilers will normally be rejected by configure tests so specifying this option should only be necessary if Magick++ fails to compile.</dd>
399<dt>--without-perl</dt>
400 <dd>disable build/install of PerlMagick, or
401 <br /><br />
402 By default, PerlMagick is conveniently compiled and installed as part of ImageMagick's normal <kbd>configure</kbd>, <kbd>make</kbd>, <kbd>sudo make install</kbd> process. When <kbd>--without-perl</kbd> is specified, you must first install ImageMagick, change to the PerlMagick subdirectory, build, and finally install PerlMagick. Note, PerlMagick is configured even if <kbd>--without-perl</kbd> is specified. If the argument <em>--with-perl=/path/to/perl</em> is supplied, <em>/../path/to/perl</em> is be taken as the PERL interpreter to use. This important in case the <kbd>perl</kbd> executable in your PATH is not PERL5, or is not the PERL you want to use.</dd>
403<dt>--with-perl=PERL</dt>
404 <dd>use specified Perl binary to configure PerlMagick.</dd>
405<dt>--with-perl-options=OPTIONS</dt>
406 <dd>options to pass on command-line when generating PerlMagick's Makefile from Makefile.PL.
407 <br /><br />
408 The PerlMagick module is normally installed using the Perl interpreter's installation PREFIX, rather than ImageMagick's. If ImageMagick's installation prefix is not the same as PERL's PREFIX, then you may find that PerlMagick's <kbd>sudo make install</kbd> step tries to install into a directory tree that you don't have write permissions to. This common when PERL is delivered with the operating system or on Internet Service Provider (ISP) web servers. If you want PerlMagick to install elsewhere, then provide a PREFIX option to PERL's configuration step via "--with-perl-options=PREFIX=/some/place". Other options accepted by MakeMaker are 'LIB', 'LIBPERL_A', 'LINKTYPE', and 'OPTIMIZE'. See the ExtUtils::MakeMaker(3) manual page for more information on configuring PERL extensions.</dd>
409<dt>--without-bzlib</dt>
410 <dd>disable BZLIB support.</dd>
411<dt>--without-dps</dt>
412 <dd>disable Display Postscript support.</dd>
413<dt>--with-fpx</dt>
414 <dd>enable FlashPIX support.</dd>
415<dt>--without-freetype</dt>
416 <dd>disable TrueType support.</dd>
417<dt>--with-gslib</dt>
418 <dd>enable Ghostscript library support.</dd>
419<dt>--without-jbig</dt>
420 <dd>disable JBIG support.</dd>
421<dt>--without-jpeg</dt>
422 <dd>disable JPEG support.</dd>
423<dt>--without-jp2</dt>
424 <dd>disable JPEG v2 support.</dd>
425<dt>--without-lcms</dt>
426 <dd>disable LCMS support.</dd>
cristy61105362010-12-19 23:22:14 +0000[diff] [blame]427<dt>--without-lzma</dt>
428 <dd>disable LZMA support.</dd>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]429<dt>--without-png</dt>
430 <dd>disable PNG support.</dd>
431<dt>--without-tiff</dt>
432 <dd>disable TIFF support.</dd>
433<dt>--without-wmf</dt>
434 <dd>disable WMF support.</dd>
435<dt>--with-fontpath</dt>
436 <dd>prepend to default font search path.</dd>
437<dt>--with-gs-font-dir</dt>
438 <dd>directory containing Ghostscript fonts.
439 <br /><br />
440 Specify the directory containing the Ghostscript Postscript Type 1 font files (e.g. <kbd>n022003l.pfb</kbd>) so that they can be rendered using the FreeType library. If the font files are installed using the default Ghostscript installation paths (<em>${prefix}/share/ghostwww/fonts</em>), they should be discovered automagically by configure and specifying this option is not necessary. Specify this option if the Ghostscript fonts fail to be located automagically, or the location needs to be overridden.</dd>
441<dt>--with-windows-font-dir</dt>
442 <dd>directory containing MS-Windows fonts.
443 <br /><br />
444 Specify the directory containing MS-Windows-compatible fonts. This not necessary when ImageMagick is running under MS-Windows.</dd>
445<dt>--without-xml</dt>
446 <dd>disable XML support.</dd>
447<dt>--without-zlib</dt>
448 <dd>disable ZLIB support.</dd>
449<dt>--without-x</dt>
450 <dd>don't use the X Window System.
451 <br /><br />
452 By default, ImageMagick uses the X11 delegate libraries if they are available. When --without-x is specified, use of X11 is disabled. The display, animate, and import sub-commands are not included. The remaining sub-commands have reduced functionality such as no access to X11 fonts (consider using Postscript or TrueType fonts instead).</dd>
453<dt>--with-share-path=DIR</dt>
454 <dd>Alternate path to share directory (default share/ImageMagick).</dd>
455<dt>--with-libstdc=DIR</dt>
456 <dd>use libstdc++ in DIR (for GNU C++).</dd>
457</dl>
458
459<p>While <kbd>configure</kbd> 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 <kbd>config.log</kbd>. 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 <kbd>config.log</kbd> are normal* because configure works by trying something and seeing if it fails. An error in <kbd>config.log</kbd> is only a problem if the test should have passed on your system.</p>
460
461<p>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.</p>
462<p>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 <a href="http://www.imagemagick.org/magick/viewforum.html?f=3">ImageMagick Defect Support Forum</a>. All bug reports should contain the operating system type (as reported by <kbd>uname -a</kbd>) and the compiler/compiler-version. A copy of the configure script output and/or the relevant portion of <kbd>config.log</kbd> file may be valuable in order to find the problem. If you post portions of <kbd>config.log</kbd>, 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.</p>
463
464<p>ImageMagick is now configured and ready to build</p>
465
466</div>
467
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]468<h2><a id="build"></a>Build</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]469<div class="doc-section">
470
471<p>Once ImageMagick is configured, these standard build targets are available from the generated <kbd>make</kbd> files:</p>
472
473<dl class="doc">
474<dt>make</dt>
475 <dd>build ImageMagick.</dd>
476<dt>sudo make install</dt>
477 <dd>install ImageMagick.</dd>
478<dt>make check</dt>
cristye6378132009-10-26 20:05:17 +0000[diff] [blame]479 <dd>Run tests using the installed ImageMagick (<kbd>sudo make install</kbd> must be done first). Ghostscript is a prerequisite, otherwise the EPS, PS, and PDF
480 tests will fail.</dd>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]481<dt>make clean</dt>
482 <dd> Remove everything in the build directory created by <kbd>make</kbd>.</dd>
483<dt>make distclean</dt>
484 <dd>remove everything in the build directory created by <kbd>configure</kbd> and <kbd>make</kbd>. This useful if you want to start over from scratch.</dd>
485<dt>make uninstall</dt>
486 <dd>Remove all files from the system which are (or would be) installed by <kbd>sudo make install</kbd> using the current configuration. Note that this target is imperfect for PerlMagick since Perl no longer supports an <em>uninstall</em> target.</dd>
487</dl>
488
489<p>In most cases you will simply wand to compile ImageMagick with this command:</p>
490
491<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>make</span></p>
492<p>Once built, you can optionally install ImageMagick on your system as discussed below.</p>
493</div>
494
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]495<h2><a id="install"></a>Install</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]496<div class="doc-section">
497
498<p>Now that ImageMagick is configured and built, type:</p>
499
500<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>make install</span></p>
501<p>to install it.</p>
502
503<p>By default, ImageMagick is installs binaries in <kbd>/../usr/local/bin</kbd>, libraries in <kbd>/../usr/local/lib</kbd>, header files in <kbd>/../usr/local/include</kbd> and documentation in <kbd>/../usr/local/share</kbd>. You can specify an alternative installation prefix other than <kbd>/../usr/local</kbd> by giving <kbd>configure</kbd> the option <em>--prefix=PATH</em>. This valuable in case you don't have privileges to install under the default paths or if you want to install in the system directories instead.</p>
504
505<p>To confirm your installation of the ImageMagick distribution was successful, ensure that the installation directory is in your executable search path and type:</p>
506
507<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>display</span></p>
508<p>The ImageMagick logo is displayed on your X11 display.</p>
509
510<p>To verify the ImageMagick build configuration, type:</p>
511
512<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>identify -list configure</span></p>
513<p>To list which image formats are supported , type:</p>
514
515<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>identify -list format</span></p>
516<p>For a more comprehensive test, you run the ImageMagick test suite by typing:</p>
517
518<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>make check</span></p>
cristye6378132009-10-26 20:05:17 +0000[diff] [blame]519<p>Ghostscript is a prerequisite, otherwise the EPS, PS, and PDF tests will fail. Note that due to differences between the developer's environment and your own it is possible that a few tests may fail even though the results are ok. Differences between the developer's environment environment and your own may include the compiler, the CPU type, and the library versions used. The ImageMagick developers use the current release of all dependent libraries.</p>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]520
521</div>
522
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]523<h2><a id="linux"></a>Linux-specific Build instructions</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]524<div class="doc-section">
525
526<p>Download <a href="ftp://ftp.imagemagick.org/pub/ImageMagick/linux/SRPMS/ImageMagick.src.rpm">ImageMagick.src.rpm</a> from <a href="ftp://ftp.imagemagick.org/pub/ImageMagick">ftp.imagemagick.org</a> or its <a href="../www/download.html">mirrors</a> and verify the distribution against its <a href="http://www.imagemagick.org/download/linux/SRPMS/digest.rdf">message digest</a>.</p>
527
528<p>Build ImageMagick with this command:</p>
529
530<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>rpmbuild --rebuild ImageMagick.src.rpm</span></p>
531<p>After the build you, locate the RPMS folder and install the ImageMagick binary RPM distribution:</p>
532
cristyec6b4752011-01-08 03:16:23 +0000[diff] [blame]533<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>rpm -ivh ImageMagick-6.6.7-?.*.rpm</span></p>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]534</div>
535
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]536<h2><a id="macosx"></a>Mac OS X-specific Build instructions</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]537<div class="doc-section">
538
539<p>Perform these steps as an administrator or with the <tt>sudo</tt> command:</p>
540
cristy6b636652009-12-05 17:16:11 +0000[diff] [blame]541<div class="doc-section">
542 <p>Install <a href="http://www.macports.org">MacPorts</a>. Download and install MacPorts and type the following commands:</p>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]543
cristy6b636652009-12-05 17:16:11 +0000[diff] [blame]544<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>sudo port -v install freetype +bytecode</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>sudo port -v install librsvg</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>sudo port -v install +graphviz +gs +wmf +jbig +jpeg2 +lcms</span></p>
545<p>This installs many of the delegate libraries ImageMagick will utilize such as JPEG and FreeType.</p>
546
547
548 <p>Install the latest <a href="http://developer.apple.com/tools/download/">Xcode</a> from Apple.</p>
549 <p>Use the <tt>port</tt> command to install any delegate libraries you require, for example:</p>
550 <p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>sudo port install jpeg</span></p> </div>
551
552<p>Now lets build ImageMagick:</p>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]553
554 <div class="doc-section">
555 <p><a href="../www/download.html">Download</a> the ImageMagick source distribution and verify the distribution against its <a href="http://www.imagemagick.org/download/digest.rdf">message digest</a>.</p>
556 <p>Unpack and change into the top-level ImageMagick directory:</p>
cristyec6b4752011-01-08 03:16:23 +0000[diff] [blame]557 <p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>tar xvfz ImageMagick-6.6.7-0.tar.gz</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>cd ImageMagick-6.6.7-0</span></p> <p>Configure ImageMagick:</p>
cristy6b636652009-12-05 17:16:11 +0000[diff] [blame]558 <p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>./configure --prefix=/opt --with-quantum-depth=16 \ <br/>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]559 --disable-dependency-tracking --with-x=yes \ <br/>
560 --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib/ \ <br/>
561 --without-perl</span></p> <p>Build ImageMagick:</p>
562 <p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>make</span></p> <p>Install ImageMagick:</p>
cristy6b636652009-12-05 17:16:11 +0000[diff] [blame]563 <p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>sudo make install</span></p> <p>To verify your install, type</p>
564
565 <p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>/opt/local/bin/identify -list font</span></p>
566 <p>to list all the fonts ImageMagick knows about.</p>
567 <p>To test the ImageMagick GUI, in a new shell, type:</p>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]568 <p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>display -display :0</span></p></div>
569
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]570</div>
571
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]572<h2><a id="mingw"></a>MinGW-specific Build instructions</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]573<div class="doc-section">
574
575<p>Although you can download and install delegate libraries yourself, many are already available in the <a href="http://gnuwin32.sourceforge.net/">GnuWin32</a> 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,</p>
576
cristyec6b4752011-01-08 03:16:23 +0000[diff] [blame]577<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>tar jxvf ImageMagick-6.6.7-?.tar.bz2</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>cd ImageMagick-6.6.7-0</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>export CPPFLAGS="-Ic:/Progra~1/GnuWin32/include"</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>export LDFLAGS="-Lc:/Progra~1/GnuWin32/lib"</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>./configure --without-perl</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>make</span><span class='crtout'></span><span class="crtprompt"> $magick&gt; </span><span class='crtin'>sudo make install</span></p></div>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]578
cristydcca3fa2010-12-29 21:50:07 +0000[diff] [blame]579<h2><a id="problems"></a>Dealing with Unexpected Problems</h2>
cristy3ed852e2009-09-05 21:47:34 +0000[diff] [blame]580<div class="doc-section">
581
582<p>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</p>
583
584<h4>Build Problems</h4>
585<p>If the build complains about missing dependencies (e.g. <em>.deps/source.PLO</em>), add <kbd>--disable-dependency-tracking</kbd> to your <kbd>configure</kbd> command line.</p>
586
587<p>Some systems may fail to link at build time due to unresolved symbols. Try adding the LDFLAGS to the <kbd>configure</kbd> command line:</p>
588
589<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>configure LDFLAGS='-L/usr/local/lib -R/usr/local/lib'</span></p>
590<h4>Dynamic Linker Run-time Bindings</h4>
591<p>On some systems, ImageMagick may not find its shared library, <em>libMagick.so</em>. Try running the <kbd>ldconfig</kbd> with the library path:</p>
592
593<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>/sbin/ldconfig /usr/local/lib</span></p>
594<p>Solaris and Linux systems have the <kbd>ldd</kbd> command which is useful to track which libraries ImageMagick depends on:</p>
595
596<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>ldd `which convert`</span></p>
597<h4>Delegate Libraries</h4>
598<p>On occasion you may receive these warnings:</p>
599<pre class="text">
600 no decode delegate for this image format
601 no encode delegate for this image format
602</pre>
603<p>This exception indicates that an external delegate library or its headers were not available when ImageMagick was built. To add support for the image format, download and install the requisite delegate library and its header files and reconfigure, rebuild, and reinstall ImageMagick. As an example, lets add support for the JPEG image format. First we install the JPEG RPMS:</p>
604
605<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>yum install libjpeg libjpeg-devel</span></p>
606<p>Now reconfigure, rebuild, and reinstall ImageMagick. To verify JPEG is now properly supported within ImageMagick, use this command:</p>
607
608<p class='crt'><span class="crtprompt"> $magick&gt; </span><span class='crtin'>identify -list format</span></p>
609<p>You should see a mode of rw- associated with the JPEG tag. This mode means the image can be read or written and can only support one image per image file.</p>
610
611<h4>PerlMagick</h4>
612<p>If PerlMagick fails to link with a message similar to <em>libperl.a is not found</em>, rerun <kbd>configure</kbd> with the <kbd>--enable-shared</kbd> or <kbd>--enable-shared --with-modules</kbd> options.</p>
613
614</div>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]615
616</div>
617
618<div id="linkbar">
cristyce69bb02010-07-27 19:49:46 +0000[diff] [blame]619 <span id="linkbar-west">&nbsp;</span>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]620 <span id="linkbar-center">
621 <a href="http://www.imagemagick.org/discourse-server/">Discourse Server</a> &bull;
cristya8902942010-07-30 00:49:52 +0000[diff] [blame]622 <a href="http://www.imagemagick.org/MagickStudio/scripts/MagickStudio.cgi">Studio</a>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]623 </span>
624 <span id="linkbar-east">&nbsp;</span>
625 </div>
626 <div class="footer">
cristy7e41fe82010-12-04 23:12:08 +0000[diff] [blame]627 <span id="footer-west">&copy; 1999-2011 ImageMagick Studio LLC</span>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]628 <span id="footer-east"> <a href="http://www.imagemagick.org/script/contact.php">Contact the Wizards</a></span>
629 </div>
630 <div style="clear: both; margin: 0; width: 100%; "></div>
cristya8902942010-07-30 00:49:52 +0000[diff] [blame]631 <script type="text/javascript">
632 var _gaq = _gaq || [];
633 _gaq.push(['_setAccount', 'UA-17690367-1']);
634 _gaq.push(['_trackPageview']);
635
636 (function() {
637 var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
638 ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
639 var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
640 })();
641 </script>
cristy3eaa0ef2010-03-06 20:35:26 +0000[diff] [blame]642</body>
643</html>