RMagick 1.15.9 README
Table Of Contents
- Contact Information
- Tips for installing and configuring ImageMagick and GraphicsMagick
- Installing RMagick
- Things that can go wrong
- More samples
- Known issues
- Reporting bugs
RMagick is an interface between the Ruby programming language and the ImageMagick and GraphicsMagick image processing libraries.
Author: Tim Hunter
O/S: Linux, Sun Solaris, Cygwin, FreeBSD, OS X.
Ruby 1.6.7 or later. You can get Ruby from http://www.ruby-lang.org. RVG requires Ruby 1.8.
Either ImageMagick 6.0.0 or later, or any release of GraphicsMagick. GraphicsMagick is a friendly fork of ImageMagick 5.5.1. You can get ImageMagick from http://www.imagemagick.org. You can get GraphicsMagick from http://www.graphicsmagick.org. ImageMagick and GraphicsMagick have slightly different capabilities. Please consult their web sites if you have questions.
Tips for installing and configuring ImageMagick and GraphicsMagick
See http://rmagick.rubyforge.org/install-faq.html for the latest version of these tips.
If you are installing RMagick by compiling the source code, I strongly encourage you to install the latest version of ImageMagick or GraphicsMagick from source. If you have never installed ImageMagick or GraphicsMagick before, I also strongly encourage you to read the README.txt file as many times as is necessary for you to understand how to configure it. ImageMagick and GraphicsMagick are large and complicated programs and can be difficult to configure. Follow these tips to minimize the amount of time you'll spend and your frustration level.
Do not simply type
./configure and expect the defaults to be correct
for you. Since you are installing ImageMagick/GraphicsMagick to use with
Ruby, consider whether you want to skip ImageMagick's/GraphicMagick's
support for Perl and C++ by using the
--without-magick-plus-plus options. Doing so will speed up the
installation process and save some disk space. You will almost certainly
want to specify the
Determine which image formats you are interested in using and make sure that you have installed the libraries that ImageMagick/GraphicsMagick uses to process these formats. ImageMagick and GraphicsMagick use additional libraries to support some image formats. If you do not install those libraries you cannot read and write those image formats. You will need to configure ImageMagick/GraphicsMagick to support the JPG, PNG, TIFF, and WMF formats in order to execute all the RMagick sample programs. See ImageMagick's or GraphicMagick's README.txt file for more information.
Once you have determined the configuration options you need, run the configure script. When it completes, read the summary output to see if configuration worked the way you expected. Here's an example of the summary output from ImageMagick's configure script. Notice that the result of each option is listed in the "Configured value" column.
Option Value ------------------------------------------------------------------------- Shared libraries --enable-shared=yes yes Static libraries --enable-static=no no Module support --with-modules=yes yes GNU ld --with-gnu-ld=yes yes LZW support --enable-lzw=yes yes Quantum depth --with-quantum-depth=8 8 Delegate Configuration: BZLIB --with-bzlib=yes yes DPS --with-dps=yes yes FlashPIX --with-fpx=yes no FreeType 2.0 --with-ttf=yes yes Ghostscript None gs (7.07.2) Ghostscript fonts --with-gs-font-dir=default /usr/share/fonts/default/Type1/ Ghostscript lib --with-gslib=no no Graphviz --with-dot=yes no JBIG --with-jbig=yes no JPEG v1 --with-jpeg=yes yes JPEG-2000 --with-jp2=yes no LCMS --with-lcms=yes yes Magick++ --with-magick-plus-plus=no no PERL --with-perl=no no PNG --with-png=yes yes TIFF --with-tiff=yes yes Windows fonts --with-windows-font-dir=/mnt/windows/windows/fonts /mnt/windows/windows/fonts/ WMF --with-wmf=yes yes X11 --with-x= yes XML --with-xml=yes yes ZLIB --with-zlib=yes yes X11 Configuration: X_CFLAGS = -I/usr/X11R6/include X_PRE_LIBS = -lSM -lICE X_LIBS = -L/usr/X11R6/lib X_EXTRA_LIBS =
If the results are not what you wanted, install any missing libraries,
choose new or different options, or whatever it takes, erase the
config.cache file, and re-run
configure. Repeat as often as necessary
before moving to the
make install steps.
Detailed information about all of ImageMagick's and GraphicsMagick's configuration options may be found in their README.txt and INSTALL.txt files.
Windows Metafile Format
As noted in the ImageMagick and GraphicsMagick README.txt files, to support images in the Windows Metafile format, ImageMagick/GraphicsMagick requires an additional library. Without this library some of the RMagick sample programs will not work. ImageMagick and GraphicsMagick require libwmf 0.2.5, 0.2.7, or 0.2.2 to support the WMF format. (Avoid libwmf 0.2.6!)
Installing RMagick is much simpler than installing ImageMagick or GraphicsMagick. Note that the make step runs all the example programs. This process both builds the example images used in the documentation and validates your RMagick installation. This step can take 5-15 minutes depending on the speed of your computer.
./configure --help to see a list of configuration options. In
addition to the regular options, there are a few RMagick-specific options:
Specify the directory to install the RMagick documentation. By default this is $prefix/share/RMagick, where $prefix is the prefix specified by --prefix. For example, to install the documentation in /home/user/RMagick, specify:
Normally the documentation installation terminates if 5 examples fail. If you use this option, the installation does not check for failing examples and will always complete. This option is useful if you're having trouble installing RMagick and you want to see all the failing examples.
--disable-htmldoc (or --enable-htmldoc=no)
By default the install process runs all the RMagick example programs and generates HTML versions of all the examples. This option causes the install process to skip this step. No documentation is installed.
If you have both ImageMagick and GraphicsMagick installed, this option will force RMagick to be configured with GraphicsMagick.
The directory for ruby extensions.
The path to set the !# line in Ruby scripts. The default is $prefix/bin/ruby.
The name of the Ruby executable. The default is
The name of the
The directory of the rbconfig.rb file to use. The default is Ruby's rbconfig.
De-compress the RMagick-1.15.9.tar.gz archive and enter the top directory. Then type:
$ ./configure <configuration options> $ make ($ su) $ make install (optionally) $ make clean
Things that can go wrong
Can't install RMagick. Can't find libMagick or one of the dependent libraries. Check the config.log file for more detailed information.
The message can also refer to "libGraphicsMagick". Typically this message means that one or more of the libraries that Imagemagick/GraphicsMagick depends on hasn't been installed. Examine the config.log file in the installation directory for any error messages. These messages typically contain enough additional information for you to be able to diagnose the problem.
Cannot open shared object file
When make is running the examples, if you get a message like this:
/home/you/RMagick-1.15.9/lib/RMagick.rb:11:in `require': libMagick.so.0: cannot open shared object file: No such file or directory - /home/you/RMagick-1.15.9/ext/RMagick/RMagick.so (LoadError)
you probably do not have the directory in which the ImageMagick or GraphicsMagick library is installed in your load path. An easy way to fix this is to define the directory in the LD_LIBRARY_PATH environment variable. For example, suppose you installed the GraphicsMagick library libGraphicsMagick.so in /usr/local/lib. (By default this is where it is installed.) Create the LD_LIBRARY_PATH variable like this:
On Linux, see
ld.so(8) for more information. On other operating
systems, see the documentation for the dynamic loading facility.
No such file or directory - "/tmp/rmagick6872.6"
When make is running the examples, if you get a message like this:
hook /home/me/src/RMagick-1.15.9/./post-setup.rb failed: No such file or directory - "/tmp/rmagick6872.6"
you probably do not have a temporary directory environment variable set. Set the TMPDIR environment variable to your temporary directory. For example:
If you upgrade to a newer release of ImageMagick or GraphicsMagick, make sure you're using a release of RMagick that supports that release. Usually I put out a new release of RMagick with every new release of ImageMagick. It's safe to install a newer release of RMagick over an earlier release.
uninstall target will uninstall RMagick completely:
You can find more sample RMagick programs in the /example directory. These programs are not installed in the RMagick documentation tree.
Please report bugs in RMagick, its documentation, or its installation programs to me via the bug tracker on the RMagick project page at RubyForge. However, I can't help with Ruby installation and configuration or ImageMagick or GraphicsMagick installation and configuration. Please report problems with that software to their respective authors or distributors.
- Simple Systems, for hosting the RMagick documentation online.
- ImageMagick Studio LLC, for ImageMagick and for hosting the RMagick documentation.
- Kaspar Schiess and Brett DiFrischia, for the MS Windows gems.
Copyright ? 2002-2007 by Timothy P. Hunter
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.