Lines Matching full:imagemagick
3 ImageMagick builds on a variety of Unix and Unix-like operating systems
6 ImageMagick.tar.gz from ftp.imagemagick.org or its mirrors and verify the
11 $magick> tar xvfz ImageMagick.tar.gz
13 Now that you have the ImageMagick Unix/Linux source distribution unpacked,
19 together to get ImageMagick compiled and installed on your system. This
21 (e.g. stdlib.h), and if any delegate libraries are available for ImageMagick
26 $magick> cd ImageMagick-7.0.7
33 ImageMagick is configured as follows. Please verify that this configuration
96 CPPFLAGS = -I/usr/local/include/ImageMagick
149 The configure script provides a number of ImageMagick specific
155 ImageMagick options represent either features to be enabled, disabled,
157 --enable-something), it enables code already present in ImageMagick. When a
176 ImageMagick built with delegates (see MAGICK PLUG-INS below) can pose
177 additional challenges. If ImageMagick is built using static libraries (the
179 either static libraries or shared libraries. However, if ImageMagick is
196 new interpreter is installed into the same directory as the ImageMagick
201 possible (note that all libraries used with ImageMagick must be shared
214 disable building an installed ImageMagick (default enabled).
216 By default the ImageMagick build is configured to formally install
218 ImageMagick. Use this option to configure ImageMagick so that it doesn't
239 Certain ImageMagick algorithms, for example convolution, can achieve
246 By default, ImageMagick is compiled with support for large files (>
248 applications which use the ImageMagick library may also require support
263 example, --with-quantum-depth=8 builds ImageMagick using 8-bit quantums.
267 important in determining the overall run-time performance of ImageMagick.
279 Larger pixel quantums can cause ImageMagick to run more slowly and to
281 cause ImageMagick to run 15% to 50% slower (and take twice as much memory)
305 installed under the directory [prefix]/lib/ImageMagick-X.X.X/modules-QN
311 is active (allowing extending an installed ImageMagick by simply copying
312 a module into place) but ImageMagick itself is not built using modules.
318 sets the maximum amount of heap memory that ImageMagick is allowed to
325 By default, the ImageMagick library is compiled with multi-thread
336 builds ImageMagick.
342 to ImageMagick. A suitable C++ compiler is required in order to build
357 of ImageMagick's normal configure, make, sudo make install process. When
358 --without-perl is specified, you must first install ImageMagick, change to
373 installation PREFIX, rather than ImageMagick's. If ImageMagick's
445 necessary when ImageMagick is running under MS-Windows.
456 By default, ImageMagick uses the X11 delegate libraries if they are
463 Alternate path to share directory (default share/ImageMagick).
468 While configure is designed to ease installation of ImageMagick, it often
470 ImageMagick. The configure script tests for headers and libraries by
486 ImageMagick Defect Support Forum. All bug reports should contain the operating
494 ImageMagick is now configured and ready to build
498 Once ImageMagick is configured, these standard build targets are available
502 build ImageMagick.
505 install ImageMagick.
508 Run tests using the installed ImageMagick (sudo make install must be
525 In most cases you will simply want to compile ImageMagick with this command:
529 Once built, you can optionally install ImageMagick on your system as
534 Now that ImageMagick is configured and built, type:
540 By default, ImageMagick is installs binaries in /../usr/local/bin, libraries
547 To confirm your installation of the ImageMagick distribution was successful,
553 The ImageMagick logo is displayed on your X11 display.
555 To verify the ImageMagick build configuration, type:
563 For a more comprehensive test, you run the ImageMagick test suite by typing:
572 ImageMagick developers use the current release of all dependent libraries.
576 Download ImageMagick.src.rpm from ftp.imagemagick.org or its mirrors and
579 Build ImageMagick with this command:
581 $magick> rpmbuild --rebuild ImageMagick.src.rpm
583 After the build you, locate the RPMS folder and install the ImageMagick
586 $magick> rpm -ivh ImageMagick-7.0.0-?.*.rpm
596 $magick> tar jxvf ImageMagick-7.0.0-?.tar.bz2
597 $magick> cd ImageMagick-7.0.0
605 Chances are the download, configure, build, and install of ImageMagick went
609 of ImageMagick
623 On some systems, ImageMagick may not find its shared library, libMagick.so. Try
629 libraries ImageMagick depends on:
641 were not available when ImageMagick was built. To add support for the image
643 files and reconfigure, rebuild, and reinstall ImageMagick. As an example,
648 Now reconfigure, rebuild, and reinstall ImageMagick. To verify JPEG is now
649 properly supported within ImageMagick, use this command: