rmagick 1.7.1 → 1.7.2

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of rmagick might be problematic. Click here for more details.

data/ChangeLog CHANGED
@@ -1,3 +1,6 @@
1
+ RMagick 1.7.2
2
+ o Fix bugs #1308, #1310, #1314, #1533
3
+
1
4
  RMagick 1.7.1
2
5
  o Fix bugs #1250, #1253
3
6
  o Tested with ImageMagick 6.1.7, Ruby 1.8.2
@@ -1,124 +1,122 @@
1
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2
- "http://www.w3.org/TR/html4/loose.dtd">
1
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
3
2
  <html>
4
3
  <head>
5
- <meta name="generator" content=
6
- "HTML Tidy for Linux/x86 (vers 1st September 2002), see www.w3.org">
7
- <title>RMagick 1.7.1 README</title>
8
- <meta http-equiv="Content-Type" content=
9
- "text/html; charset=ISO-8859-1">
10
- <meta name="GENERATOR" content="Quanta Plus">
4
+ <title>RMagick 1.7.2 README</title>
5
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
6
+ <meta name="GENERATOR" content="BlueCloth">
11
7
  </head>
12
8
  <body>
13
- <div align="center">
14
- <h1>RMagick 1.7.1</h1>
15
- <h2>README</h2>
16
- <h4>12/25/04</h4>
17
- </div>
18
- <h2>Table of Contents</h2>
19
- <ul>
20
- <li><a href="#introduction">Introduction</a></li>
21
- <li><a href="#contact_information">Contact
22
- information</a></li>
23
- <li><a href="#prerequisites">Prerequisites</a></li>
24
- <li><a href="#tips">Tips for installing and configuring
25
- ImageMagick and GraphicsMagick</a></li>
26
- <li><a href="#installing_rmagick">Installing RMagick</a>
27
- <ul>
28
- <li><a href="#configuration_options">Configuration
29
- options</a></li>
30
- <li><a href="#running">Running the configure and make
31
- scripts</a></li>
32
- </ul>
33
- </li>
34
- <li><a href="#things_that_can_go_wrong">Things that can go
35
- wrong</a></li>
36
- <li><a href="#upgrading">Upgrading</a></li>
37
- <li><a href="#uninstalling">Uninstalling</a></li>
38
- <li><a href="#more_samples">More samples</a></li>
39
- <li><a href="#undocumented_features">Undocumented
40
- features</a></li>
41
- <li><a href="#known_issues">Known issues</a></li>
42
- <li><a href="#reporting_bugs">Reporting bugs</a></li>
43
- <li><a href="#credits">Credits</a></li>
44
- <li><a href="#license">License</a></li>
45
- </ul>
46
- <h2><a name="introduction">Introduction</a></h2>
47
- <p>RMagick is an interface between the Ruby programming
48
- language and the ImageMagick and GraphicsMagick image
49
- processing libraries.</p>
50
- <h2><a name="contact_information">Contact Information</a></h2>
51
- <b>Author:</b>&nbsp;Tim Hunter<br>
52
- <b>Email:</b>&nbsp;<a href=
53
- "mailto:rmagick@rubyforge.org">rmagick@rubyforge.org</a><br>
54
- <b>RubyForge:</b>&nbsp;<a href="http://rubyforge.org/projects/rmagick">RMagick</a><br>
55
-
56
- <h2><a name="prerequisites">Prerequisites</a></h2>
57
- <dl>
58
- <dt><b>O/S</b></dt>
59
- <dd>Linux, Sun Solaris, Cygwin, FreeBSD, MS Windows 98 and later.</dd>
60
- <dt><b>Ruby</b></dt>
61
- <dd>Ruby 1.6.7 or later. You can get Ruby from
62
- <a href="http://www.ruby-lang.org">www.ruby-lang.org</a></dd>
63
- </dl>
64
- One of
65
- <dl>
66
- <dt><b>ImageMagick</b></dt>
67
- <dd>ImageMagick 6.0.0 or later. You can get ImageMagick
68
- from <a href="http://www.imagemagick.org">www.imagemagick.org</a>.</dd>
69
- <dt><b>GraphicsMagick</b></dt>
70
- <dd>GraphicsMagick is a friendly fork of ImageMagick 5.5.1.
71
- You can get GraphicsMagick from <a href="http://www.graphicsmagick.org">www.graphicsmagick.org</a>.</dd>
72
- </dl>
73
- <p>You only need one of ImageMagick or GraphicsMagick. RMagick
74
- works equally well with both. Some RMagick methods may not be supported in one or the other library.</p>
75
- <h2><a name="tips">Tips for installing and configuring
76
- ImageMagick and GraphicsMagick</a></h2>
77
- <p>if you are installing RMagick by compiling the source code,
78
- I <em>strongly</em> encourage you to install the latest version
79
- of ImageMagick or GraphicsMagick <em>from source</em>.
80
- If you have never installed ImageMagick or GraphicsMagick
81
- before, I also strongly encourage you to
82
- read the README.txt file as many times as is necessary for you
83
- to understand how to configure it. ImageMagick and
84
- GraphicsMagick are large and complicated programs and can be
85
- difficult to configure. Follow these tips to minimize the
86
- amount of time you'll spend and your frustration level.</p>
87
- <p>Do <i>not</i> simply type ./configure and expect the
88
- defaults to be correct for you. Since you are installing ImageMagick/GraphicsMagick to use
89
- with Ruby, consider whether you want to skip
90
- ImageMagick's/GraphicMagicks' support for Perl and C++ by using
91
- the --without-perl and --without-magick-plus-plus options.
92
- Doing so will speed up the installation process and save some
93
- disk space. You will almost certainly want to specify the
94
- --enable-shared and --disable-static options.</p>
95
- <p>Determine which image formats you are interested in using
96
- and make sure that you have installed the libraries that
97
- ImageMagick/GraphicsMagick uses to process these formats.
98
- ImageMagick and GraphicsMagick use additional libraries to
99
- support some image formats. If you do not install those
100
- libraries you cannot read and write those image formats. You
101
- will need to configure ImageMagick/GraphicsMagick to support
102
- the JPG, PNG, TIFF, and WMF formats in order to execute all the
103
- RMagick sample programs. See ImageMagick's or GraphicMagick's
104
- README.txt file for more information.</p>
105
- <p>Once you have determined the configuration options you need,
106
- run the configure script. When it completes, read the summary
107
- output to see if configuration worked the way you expected.
108
- Here's an example of the summary output from ImageMagick's
109
- configure script. Notice that the result of each option is
110
- listed in the "Configured value" column.</p>
111
- <pre>
112
- Option Value
113
- -------------------------------------------------------------------------
114
- Shared libraries --enable-shared=yes yes
9
+ <p>RMagick 1.7.2</p>
10
+
11
+ <pre><code>README
12
+
13
+
14
+ 02/23/05
15
+
16
+
17
+ Table of Contents
18
+
19
+ * Introduction &lt;#introduction&gt;
20
+ * Contact information &lt;#contact_information&gt;
21
+ * Prerequisites &lt;#prerequisites&gt;
22
+ * Tips for installing and configuring ImageMagick and GraphicsMagick
23
+ &lt;#tips&gt;
24
+ * Installing RMagick &lt;#installing_rmagick&gt;
25
+ o Configuration options &lt;#configuration_options&gt;
26
+ o Running the configure and make scripts &lt;#running&gt;
27
+ * Things that can go wrong &lt;#things_that_can_go_wrong&gt;
28
+ * Upgrading &lt;#upgrading&gt;
29
+ * Uninstalling &lt;#uninstalling&gt;
30
+ * More samples &lt;#more_samples&gt;
31
+ * Undocumented features &lt;#undocumented_features&gt;
32
+ * Known issues &lt;#known_issues&gt;
33
+ * Reporting bugs &lt;#reporting_bugs&gt;
34
+ * Credits &lt;#credits&gt;
35
+ * License &lt;#license&gt;
36
+
37
+
38
+ Introduction
39
+ </code></pre>
40
+
41
+ <p>RMagick is an interface between the Ruby programming language and the
42
+ ImageMagick and GraphicsMagick image processing libraries.</p>
43
+
44
+ <pre><code>Contact Information
45
+ </code></pre>
46
+
47
+ <p><em>Author:</em> Tim Hunter
48
+ <em>Email:</em> rmagick@rubyforge.org <mailto:rmagick@rubyforge.org>
49
+ <em>RubyForge:</em> RMagick <a href="http://rubyforge.org/projects/rmagick">http://rubyforge.org/projects/rmagick</a></p>
50
+
51
+ <pre><code>Prerequisites
52
+ </code></pre>
53
+
54
+ <p><em>O/S</em>
55
+ Linux, Sun Solaris, Cygwin, FreeBSD, MS Windows 98 and later.
56
+ <em>Ruby</em>
57
+ Ruby 1.6.7 or later. You can get Ruby from www.ruby-lang.org
58
+ <a href="http://www.ruby-lang.org">http://www.ruby-lang.org</a></p>
59
+
60
+ <p>One of</p>
61
+
62
+ <p><em>ImageMagick</em>
63
+ ImageMagick 6.0.0 or later. You can get ImageMagick from
64
+ www.imagemagick.org <a href="http://www.imagemagick.org">http://www.imagemagick.org</a>.
65
+ <em>GraphicsMagick</em>
66
+ GraphicsMagick is a friendly fork of ImageMagick 5.5.1. You can get
67
+ GraphicsMagick from www.graphicsmagick.org
68
+ <a href="http://www.graphicsmagick.org">http://www.graphicsmagick.org</a>.</p>
69
+
70
+ <p>You only need one of ImageMagick or GraphicsMagick. RMagick works
71
+ equally well with both. Some RMagick methods may not be supported in one
72
+ or the other library.</p>
73
+
74
+ <pre><code>Tips for installing and configuring ImageMagick and GraphicsMagick
75
+ </code></pre>
76
+
77
+ <p>if you are installing RMagick by compiling the source code, I /strongly/
78
+ encourage you to install the latest version of ImageMagick or
79
+ GraphicsMagick /from source/. If you have never installed ImageMagick or
80
+ GraphicsMagick before, I also strongly encourage you to read the
81
+ README.txt file as many times as is necessary for you to understand how
82
+ to configure it. ImageMagick and GraphicsMagick are large and
83
+ complicated programs and can be difficult to configure. Follow these
84
+ tips to minimize the amount of time you'll spend and your frustration level.</p>
85
+
86
+ <p>Do /not/ simply type ./configure and expect the defaults to be correct
87
+ for you. Since you are installing ImageMagick/GraphicsMagick to use with
88
+ Ruby, consider whether you want to skip ImageMagick's/GraphicMagicks'
89
+ support for Perl and C++ by using the --without-perl and
90
+ --without-magick-plus-plus options. Doing so will speed up the
91
+ installation process and save some disk space. You will almost certainly
92
+ want to specify the --enable-shared and --disable-static options.</p>
93
+
94
+ <p>Determine which image formats you are interested in using and make sure
95
+ that you have installed the libraries that ImageMagick/GraphicsMagick
96
+ uses to process these formats. ImageMagick and GraphicsMagick use
97
+ additional libraries to support some image formats. If you do not
98
+ install those libraries you cannot read and write those image formats.
99
+ You will need to configure ImageMagick/GraphicsMagick to support the
100
+ JPG, PNG, TIFF, and WMF formats in order to execute all the RMagick
101
+ sample programs. See ImageMagick's or GraphicMagick's README.txt file
102
+ for more information.</p>
103
+
104
+ <p>Once you have determined the configuration options you need, run the
105
+ configure script. When it completes, read the summary output to see if
106
+ configuration worked the way you expected. Here's an example of the
107
+ summary output from ImageMagick's configure script. Notice that the
108
+ result of each option is listed in the "Configured value" column.</p>
109
+
110
+ <h2> Option Value</h2>
111
+
112
+ <p>Shared libraries --enable-shared=yes yes
115
113
  Static libraries --enable-static=no no
116
114
  Module support --with-modules=yes yes
117
115
  GNU ld --with-gnu-ld=yes yes
118
116
  LZW support --enable-lzw=yes yes
119
- Quantum depth --with-quantum-depth=8 8
117
+ Quantum depth --with-quantum-depth=8 8</p>
120
118
 
121
- Delegate Configuration:
119
+ <p>Delegate Configuration:
122
120
  BZLIB --with-bzlib=yes yes
123
121
  DPS --with-dps=yes yes
124
122
  FlashPIX --with-fpx=yes no
@@ -139,266 +137,288 @@ Windows fonts --with-windows-font-dir=/mnt/windows/windows/fonts /mnt/win
139
137
  WMF --with-wmf=yes yes
140
138
  X11 --with-x= yes
141
139
  XML --with-xml=yes yes
142
- ZLIB --with-zlib=yes yes
140
+ ZLIB --with-zlib=yes yes</p>
143
141
 
144
- X11 Configuration:
142
+ <p>X11 Configuration:
145
143
  X_CFLAGS = -I/usr/X11R6/include
146
- X_PRE_LIBS = -lSM -lICE
144
+ X<em>PRE</em>LIBS = -lSM -lICE
147
145
  X_LIBS = -L/usr/X11R6/lib
148
- X_EXTRA_LIBS =
149
- </pre>
150
- <p>If the results are not what you wanted, install any missing
151
- libraries, choose new or different options, or whatever it
152
- takes, erase the config.cache file, and re-run configure.
153
- Repeat as often as necessary before moving to the `make' and
154
- `make install' steps.</p>
155
- <p>Detailed information about all of ImageMagick's and
156
- GraphicsMagick's configuration options may be found in their
157
- README.txt and INSTALL.txt files.</p>
158
- <h4>Windows Metafile Format</h4>
159
- <p>As noted in the ImageMagick and GraphicsMagick README.txt
160
- files, to support images in the Windows Metafile format,
161
- ImageMagick/GraphicsMagick requires an additional library.
162
- Without this library some of the RMagick sample programs will
163
- not work. ImageMagick and GraphicsMagick require libwmf 0.2.5,
164
- 0.2.7, or 0.2.2 to support the WMF format. (Avoid libwmf
165
- 0.2.6!)</p>
166
- <h2><a name="installing_rmagick">Installing RMagick</a></h2>
167
- <p>Installing RMagick is much simpler than installing
168
- ImageMagick or GraphicsMagick. Note that the <i>make</i> step
169
- runs all the example programs. This process both builds the
170
- example images used in the documentation and validates your
171
- RMagick installation. This step can take 5-15 minutes depending
172
- on the speed of your computer.</p>
173
- <h4><a name="configuration_options">Configuration
174
- options</a></h4>
175
- <p>Type <code>./configure --help</code> to see a list of
176
- configuration options. In addition to the regular options,
177
- there are a few RMagick-specific options:</p>
178
- <dl>
179
- <dt>--with-doc-dir=directory</dt>
180
- <dd>
181
- Specify the directory to install the RMagick documentation.
182
- By default this is $prefix/share/RMagick, where $prefix is
183
- the prefix specified by --prefix. For example, to install
184
- the documentation in /home/user/RMagick, specify:
185
- <pre>
186
- ./configure --with-doc-dir=/home/user/RMagick
187
- </pre>
188
- </dd>
189
- <dt>--enable-allow-example-errors</dt>
190
- <dd>Normally the documentation installation terminates if 5
191
- examples fail. If you use this option, the installation does
192
- not check for failing examples and will always complete. This
193
- option is useful if you're having trouble installing RMagick
194
- and you want to see all the failing examples.</dd>
195
- <dt>--with-graphics-magick</dt>
196
- <dd>If you have both ImageMagick and GraphicsMagick installed, this option will force RMagick to be configured with GraphicsMagick.</dd>
197
- <dt>--with-so-dir=directory</dt>
198
- <dd>The directory for ruby extensions.</dd>
199
- <dt>--with-ruby-path=directory</dt>
200
- <dd>The path to set the !# line in Ruby scripts. The default is <code>$prefix/bin/ruby</code>.</dd>
201
- <dt>--with-ruby-prog=name</dt>
202
- <dd>The name of the Ruby executable. The default is <code>ruby</code>.</dd>
203
- <dt>--with-make-prog=name</dt>
204
- <dd>The name of the <code>make</code> program.</dd>
205
- <dt>--with-rbconfig=path</dt>
206
- <dd>The path to the rbconfig.rb file to use. The default is Ruby's rbconfig.</dd>
207
- </dl>
208
- <br>
209
-
210
- <h4><a name="running">Running the <code>configure</code> and
211
- <code>make</code> scripts</a></h4>
212
- <p>De-compress the RMagick-1.7.1.tar.gz archive and
213
- enter the top directory. Then type:</p>
214
- <pre>
215
- $ ./configure &lt;configuration options&gt;
216
- $ make
217
- ($ su)
146
+ X<em>EXTRA</em>LIBS =</p>
147
+
148
+ <p>If the results are not what you wanted, install any missing libraries,
149
+ choose new or different options, or whatever it takes, erase the
150
+ config.cache file, and re-run configure. Repeat as often as necessary
151
+ before moving to the <code>make' and</code>make install' steps.</p>
152
+
153
+ <p>Detailed information about all of ImageMagick's and GraphicsMagick's
154
+ configuration options may be found in their README.txt and INSTALL.txt
155
+ files.</p>
156
+
157
+ <pre><code> Windows Metafile Format
158
+ </code></pre>
159
+
160
+ <p>As noted in the ImageMagick and GraphicsMagick README.txt files, to
161
+ support images in the Windows Metafile format,
162
+ ImageMagick/GraphicsMagick requires an additional library. Without this
163
+ library some of the RMagick sample programs will not work. ImageMagick
164
+ and GraphicsMagick require libwmf 0.2.5, 0.2.7, or 0.2.2 to support the
165
+ WMF format. (Avoid libwmf 0.2.6!)</p>
166
+
167
+ <pre><code>Installing RMagick
168
+ </code></pre>
169
+
170
+ <p>Installing RMagick is much simpler than installing ImageMagick or
171
+ GraphicsMagick. Note that the /make/ step runs all the example programs.
172
+ This process both builds the example images used in the documentation
173
+ and validates your RMagick installation. This step can take 5-15 minutes
174
+ depending on the speed of your computer.</p>
175
+
176
+ <pre><code> Configuration options
177
+ </code></pre>
178
+
179
+ <p>Type |./configure --help| to see a list of configuration options. In
180
+ addition to the regular options, there are a few RMagick-specific options:</p>
181
+
182
+ <p>--with-doc-dir=directory
183
+ Specify the directory to install the RMagick documentation. By
184
+ default this is $prefix/share/RMagick, where $prefix is the prefix
185
+ specified by --prefix. For example, to install the documentation in
186
+ /home/user/RMagick, specify:</p>
187
+
188
+ <p>./configure --with-doc-dir=/home/user/RMagick</p>
189
+
190
+ <p>--enable-allow-example-errors
191
+ Normally the documentation installation terminates if 5 examples
192
+ fail. If you use this option, the installation does not check for
193
+ failing examples and will always complete. This option is useful if
194
+ you're having trouble installing RMagick and you want to see all the
195
+ failing examples.
196
+ --with-graphics-magick
197
+ If you have both ImageMagick and GraphicsMagick installed, this
198
+ option will force RMagick to be configured with GraphicsMagick.
199
+ --with-so-dir=directory
200
+ The directory for ruby extensions.
201
+ --with-ruby-path=directory
202
+ The path to set the !# line in Ruby scripts. The default is
203
+ |$prefix/bin/ruby|.
204
+ --with-ruby-prog=name
205
+ The name of the Ruby executable. The default is |ruby|.
206
+ --with-make-prog=name
207
+ The name of the |make| program.
208
+ --with-rbconfig=path
209
+ The path to the rbconfig.rb file to use. The default is Ruby's rbconfig.</p>
210
+
211
+ <pre><code> Running the |configure| and |make| scripts
212
+ </code></pre>
213
+
214
+ <p>De-compress the RMagick-1.7.2.tar.gz archive and enter the
215
+ top directory. Then type:</p>
216
+
217
+ <pre><code>$ ./configure &lt;configuration options&gt;
218
+ $ make
219
+ </code></pre>
220
+
221
+ <p>($ su)
218
222
  $ make install
219
223
  (optionally)
220
- $ make clean
221
- </pre>
222
- <h2><a name="things_that_can_go_wrong">Things that can go
223
- wrong</a></h2>
224
- <dl>
225
- <dt><b>Cannot open shared object file</b></dt>
226
- <dd>
227
- <p>When <code>make</code> is running the examples, if you get
228
- a message like this:</p>
229
- <pre>
230
- /home/you/RMagick-1.7.1/lib/RMagick.rb:11:in `require': libMagick.so.0:
224
+ $ make clean</p>
225
+
226
+ <pre><code>Things that can go wrong
227
+ </code></pre>
228
+
229
+ <p><em>Cannot open shared object file</em></p>
230
+
231
+ <pre><code>When |make| is running the examples, if you get a message like this:
232
+ </code></pre>
233
+
234
+ <p>/home/you/RMagick-1.7.2/lib/RMagick.rb:11:in 'require': libMagick.so.0:
231
235
  cannot open shared object file: No such file or directory -
232
- /home/you/RMagick-1.7.1/ext/RMagick/RMagick.so (LoadError)
233
- </pre>
234
- <p>you probably do not have the directory in which the
235
- ImageMagick or GraphicsMagick library is installed in your
236
- load path. An easy way to fix this is to define the
237
- directory in the LD_LIBRARY_PATH environment variable. For
238
- example, suppose you installed the GraphicsMagick library
239
- libGraphicsMagick.so in /usr/local/lib. (By default this is
240
- where it is installed.) Create the LD_LIBRARY_PATH variable
241
- like this:</p>
242
- <pre>
243
- export LD_LIBRARY_PATH=/usr/local/lib
244
- </pre>
245
- <p>On Linux, see <code>ld(1)</code> and
246
- <code>ld.so(8)</code> for more information. On other
247
- operating systems, see the documentation for the dynamic
248
- loading facility.</p>
249
- </dd>
250
- <dt><b>No such file or directory -
251
- "/tmp/rmagick6872.6"</b></dt>
252
- <dd>
253
- <p>When <code>make</code> is running the examples, if you get
254
- a message like this:</p>
255
- <pre>
256
- hook /home/me/src/RMagick-1.7.1/./post-setup.rb failed:
257
- No such file or directory - "/tmp/rmagick6872.6"
258
- </pre>
259
- <p>you probably do not have a temporary directory
260
- environment variable set. Set the TMPDIR environment
261
- variable to your temporary directory. For example:</p>
262
- <pre>
263
- export TMPDIR=/home/me/tmp
264
- </pre>
265
- </dd>
266
- </dl>
267
- <h2><a name="upgrading">Upgrading</a></h2>
268
- <p>If you upgrade to a newer release of ImageMagick or
269
- GraphicsMagick, make sure you're using a release of RMagick
270
- that supports that release. Usually I put out a new release of
271
- RMagick with every new release of ImageMagick. It's safe to
272
- install a newer release of RMagick over an earlier release.</p>
273
- <h2><a name="uninstalling">Uninstalling</a></h2>
274
- <p>The `uninstall' target will uninstall RMagick completely:</p>
275
- <blockquote><code>make uninstall</code></blockquote>
276
- <h2>More samples</h2>
277
- <p>You can find more sample RMagick programs in the /example
278
- directory. These programs are not installed in the RMagick
279
- documentation tree.</p>
280
- <h2><a name="undocumented_features">Undocumented
281
- features</a></h2>
282
- <p>This release includes an extra feature that isn't in the
283
- documentation. The Magick module defines two methods that
284
- control ImageMagick's logging function. This function is not
285
- officially documented by ImageMagick, so I have decided not to
286
- add them to RMagick's documentation. However, you may find them
287
- helpful for debugging your application. (Caveat: these two
288
- methods may change behavior or be removed without advance
289
- notice! You are on your own!)</p>
290
- <p><i>Magick::set_log_event_mask(event [,...]) -&gt;
291
- Magick</i></p>
292
- <p>The arguments are one or more "event domains". The
293
- set_log_event_mask method recognizes these event domains:
294
- "all", "annotate", "blob", "cache", "coder", "configure",
295
- "deprecate", "draw", "locale", "none", "resource", "transform", "user",
296
- and "x11". ImageMagick events that match the mask are logged.
297
- The default domain is "none". For example,</p>
298
- <pre>
299
- Magick::set_log_event_mask("render")
300
-
301
- </pre>
302
- <p>Logging is controlled by the log.mgk file, which may be
303
- found in the same directory as the delegates.mgk files. (See
304
- ImageMagick's README.txt file.) The purpose of the entries in
305
- this file is undocumented, so your guess is as good as mine.
306
- Also, the meaning of the event domains and exactly what events
307
- are logged are undocumented.</p>
308
- <p><i>Magick::set_log_format(format) -&gt; Magick</i></p>
309
- <p>The default log format is described in the log.mgk file.
310
- This method allows you to redefine the format at run-time. The
311
- format argument is a string similar to an fprintf format
312
- string. Each line in the log has the format described by the
313
- format string. Characters that are not control characters are
314
- printed as-is. The control characters are:</p>
315
- <pre>
316
- %t - the current time
317
- %r - the elapsed time
318
- %u - the user time
319
- %p - the pid (process id)
320
- %m - the name of the ImageMagick source file that contains the
321
- function that generated the event
322
- %f - the name of the ImageMagick function that generated the
323
- event
324
- %l - the line number in the source file
325
- %d - the event domain (one of the event mask strings listed above)
326
- %e - the event name
327
- </pre>
328
- <p>For example, the default log format is:</p>
329
- <pre>
330
- Magick::set_log_format("%t %r %u %p %m/%f/%l/%d:\n %e")
331
- </pre>
332
- <h2><a name="known_issues">Known issues</a></h2>
333
- <ol>
334
- <li>
335
- gcc 3.2, during the "install.rb setup" step, issues the
336
- warning:
337
- <pre>
338
- cc1: warning: changing search order for system directory "/usr/local/include"
339
- cc1: warning: as it has already been specified as a non-system directory
340
- </pre>
341
- This does not indicate a problem.
342
- </li>
343
- <li>
344
- With older releases of ImageMagick you may see the warning:
345
- <pre>
346
- /usr/include/sys/ipc.h:25:3: warning: #warning "Files using this header must be compiled with _SVID_SOURCE or _XOPEN_SOURCE"
347
- </pre>
348
- This is harmless.
349
- </li>
350
- </ol>
351
- <h2><a name="reporting_bugs">Reporting bugs</a></h2>
352
- <p>Please report bugs in RMagick, its documentation, or its
353
- installation programs to me via the bug tracker on the
354
- <a href="http://rubyforge.org/projects/rmagick/">RMagick project page</a>
355
- at RubyForge.
356
- However, I cannot help with Ruby installation and configuration
357
- or ImageMagick or GraphicsMagick installation and
358
- configuration. Please report problems with that software to
359
- their respective authors or distributors.</p>
360
- <h2><a name="credits">Credits</a></h2>
361
- <p>Thanks to</p>
362
- <ul>
363
- <li>Akinori MUSHA, for his work making RMagick available on
364
- FreeBSD.</li>
365
- <li>Tom Payne, for reporting bugs, sending me the Ruby 1.8.0
366
- patches, and for the Gentoo ebuild.</li>
367
- <li>Bob Friesenhahn, for GraphicsMagick. Also for his help with
368
- the RMagick installation and many other things.</li>
369
- <li>
370
- Simple Systems, for hosting the RMagick documentation online.
371
- </li>
372
- <li>Mike Williams, for the RMagick Debian package</li>
373
- <li>ImageMagick Studio LLC, for ImageMagick and for
374
- hosting the RMagick documentation.</li>
375
- <li>Kaspar Schiess, for the MS Windows gem.</li>
376
- </ul>
377
- <h2><a name="license">License</a></h2>
378
-
379
- <div style="padding: 1em; margin-left: 5%; margin-right: 5%; background-color: #dcdcdc">
380
-
381
- <p>Copyright &copy; 2004 by Timothy P. Hunter</p>
382
- <p>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:
383
- </p>
384
-
385
-
386
- <p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p>
387
-
388
-
389
-
390
- <p>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. </p> </div>
391
- <div align="center" style="padding: 3em">
392
- <table>
393
- <tr>
394
- <td>
395
- <a href="http://www.opensource.org/docs/definition.php">
396
- <img src="http://www.opensource.org/trademarks/osi-certified/web/osi-certified-60x50.gif"
397
- border="0" width="60" height="50"></a>
398
- <td align="center">
399
- <p><strong>This software is OSI Certified Open Source Software.<br>
400
- OSI Certified is a certification mark of the Open Source Initiative.</strong></p>
401
- </td></tr></table>
402
- </div>
236
+ /home/you/RMagick-1.7.2/ext/RMagick/RMagick.so (LoadError)</p>
237
+
238
+ <pre><code>you probably do not have the directory in which the ImageMagick or
239
+ GraphicsMagick library is installed in your load path. An easy way
240
+ to fix this is to define the directory in the LD_LIBRARY_PATH
241
+ environment variable. For example, suppose you installed the
242
+ GraphicsMagick library libGraphicsMagick.so in /usr/local/lib. (By
243
+ default this is where it is installed.) Create the LD_LIBRARY_PATH
244
+ variable like this:
245
+ </code></pre>
246
+
247
+ <p>export LD<em>LIBRARY</em>PATH=/usr/local/lib</p>
248
+
249
+ <pre><code>On Linux, see |ld(1)| and |ld.so(8)| for more information. On other
250
+ operating systems, see the documentation for the dynamic loading
251
+ facility.
252
+ </code></pre>
253
+
254
+ <p><em>No such file or directory - "/tmp/rmagick6872.6"</em></p>
255
+
256
+ <pre><code>When |make| is running the examples, if you get a message like this:
257
+ </code></pre>
258
+
259
+ <p>hook /home/me/src/RMagick-1.7.2/./post-setup.rb failed:
260
+ No such file or directory - "/tmp/rmagick6872.6"</p>
261
+
262
+ <pre><code>you probably do not have a temporary directory environment variable
263
+ set. Set the TMPDIR environment variable to your temporary
264
+ directory. For example:
265
+ </code></pre>
266
+
267
+ <p>export TMPDIR=/home/me/tmp</p>
268
+
269
+ <pre><code>Upgrading
270
+ </code></pre>
271
+
272
+ <p>If you upgrade to a newer release of ImageMagick or GraphicsMagick, make
273
+ sure you're using a release of RMagick that supports that release.
274
+ Usually I put out a new release of RMagick with every new release of
275
+ ImageMagick. It's safe to install a newer release of RMagick over an
276
+ earlier release.</p>
277
+
278
+ <pre><code>Uninstalling
279
+ </code></pre>
280
+
281
+ <p>The 'uninstall' target will uninstall RMagick completely:</p>
282
+
283
+ <pre><code>|make uninstall|
284
+
285
+
286
+ More samples
287
+ </code></pre>
288
+
289
+ <p>You can find more sample RMagick programs in the /example directory.
290
+ These programs are not installed in the RMagick documentation tree.</p>
291
+
292
+ <pre><code>Undocumented features
293
+ </code></pre>
294
+
295
+ <p>This release includes an extra feature that isn't in the documentation.
296
+ The Magick module defines two methods that control ImageMagick's logging
297
+ function. This function is not officially documented by ImageMagick, so
298
+ I have decided not to add them to RMagick's documentation. However, you
299
+ may find them helpful for debugging your application. (Caveat: these two
300
+ methods may change behavior or be removed without advance notice! You
301
+ are on your own!)</p>
302
+
303
+ <p>/Magick::set<em>log</em>event_mask(event [,...]) -> Magick/</p>
304
+
305
+ <p>The arguments are one or more "event domains". The set<em>log</em>event_mask
306
+ method recognizes these event domains: "all", "annotate", "blob",
307
+ "cache", "coder", "configure", "deprecate", "draw", "locale", "none",
308
+ "resource", "transform", "user", and "x11". ImageMagick events that
309
+ match the mask are logged. The default domain is "none". For example,</p>
310
+
311
+ <pre><code> Magick::set_log_event_mask("render")
312
+ </code></pre>
313
+
314
+ <p>Logging is controlled by the log.mgk file, which may be found in the
315
+ same directory as the delegates.mgk files. (See ImageMagick's README.txt
316
+ file.) The purpose of the entries in this file is undocumented, so your
317
+ guess is as good as mine. Also, the meaning of the event domains and
318
+ exactly what events are logged are undocumented.</p>
319
+
320
+ <p>/Magick::set<em>log</em>format(format) -> Magick/</p>
321
+
322
+ <p>The default log format is described in the log.mgk file. This method
323
+ allows you to redefine the format at run-time. The format argument is a
324
+ string similar to an fprintf format string. Each line in the log has the
325
+ format described by the format string. Characters that are not control
326
+ characters are printed as-is. The control characters are:</p>
327
+
328
+ <pre><code> %t - the current time
329
+ %r - the elapsed time
330
+ %u - the user time
331
+ %p - the pid (process id)
332
+ %m - the name of the ImageMagick source file that contains the
333
+ function that generated the event
334
+ %f - the name of the ImageMagick function that generated the
335
+ event
336
+ %l - the line number in the source file
337
+ %d - the event domain (one of the event mask strings listed above)
338
+ %e - the event name
339
+ </code></pre>
340
+
341
+ <p>For example, the default log format is:</p>
342
+
343
+ <pre><code> Magick::set_log_format("%t %r %u %p %m/%f/%l/%d:\n %e")
344
+
345
+
346
+ Known issues
347
+ </code></pre>
348
+
349
+ <ol>
350
+ <li>gcc 3.2, during the "install.rb setup" step, issues the warning:</li>
351
+ </ol>
352
+
353
+ <p>cc1: warning: changing search order for system directory "/usr/local/include"
354
+ cc1: warning: as it has already been specified as a non-system directory</p>
355
+
356
+ <pre><code> This does not indicate a problem.
357
+ </code></pre>
358
+
359
+ <ol>
360
+ <li>With older releases of ImageMagick you may see the warning:</li>
361
+ </ol>
362
+
363
+ <p>/usr/include/sys/ipc.h:25:3: warning: #warning "Files using this header must be compiled with <em>SVID</em>SOURCE or <em>XOPEN</em>SOURCE"</p>
364
+
365
+ <pre><code> This is harmless.
366
+
367
+
368
+ Reporting bugs
369
+ </code></pre>
370
+
371
+ <p>Please report bugs in RMagick, its documentation, or its installation
372
+ programs to me via the bug tracker on the RMagick project page
373
+ <a href="http://rubyforge.org/projects/rmagick/">http://rubyforge.org/projects/rmagick/</a> at RubyForge. However, I cannot
374
+ help with Ruby installation and configuration or ImageMagick or
375
+ GraphicsMagick installation and configuration. Please report problems
376
+ with that software to their respective authors or distributors.</p>
377
+
378
+ <pre><code>Credits
379
+ </code></pre>
380
+
381
+ <p>Thanks to</p>
382
+
383
+ <pre><code>* Akinori MUSHA, for his work making RMagick available on FreeBSD.
384
+ * Tom Payne, for reporting bugs, sending me the Ruby 1.8.0 patches,
385
+ and for the Gentoo ebuild.
386
+ * Bob Friesenhahn, for GraphicsMagick. Also for his help with the
387
+ RMagick installation and many other things.
388
+ * Simple Systems, for hosting the RMagick documentation online.
389
+ * Mike Williams, for the RMagick Debian package
390
+ * ImageMagick Studio LLC, for ImageMagick and for hosting the
391
+ RMagick documentation.
392
+ * Kaspar Schiess, for the MS Windows gem.
393
+
394
+
395
+ License
396
+ </code></pre>
397
+
398
+ <p>Copyright � 2004 by Timothy P. Hunter</p>
399
+
400
+ <p>Permission is hereby granted, free of charge, to any person obtaining a
401
+ copy of this software and associated documentation files (the
402
+ "Software"), to deal in the Software without restriction, including
403
+ without limitation the rights to use, copy, modify, merge, publish,
404
+ distribute, sublicense, and/or sell copies of the Software, and to
405
+ permit persons to whom the Software is furnished to do so, subject to
406
+ the following conditions:</p>
407
+
408
+ <p>The above copyright notice and this permission notice shall be included
409
+ in all copies or substantial portions of the Software.</p>
410
+
411
+ <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
412
+ OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
413
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
414
+ IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
415
+ CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
416
+ TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
417
+ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
418
+
419
+ <p><a href="http://www.opensource.org/docs/definition.php">http://www.opensource.org/docs/definition.php</a></p>
420
+
421
+ <p>*This software is OSI Certified Open Source Software.
422
+ OSI Certified is a certification mark of the Open Source Initiative.*</p>
403
423
  </body>
404
424
  </html>