magick-rust
A somewhat safe Rust interface to the ImageMagick system, in particular, the MagickWand library. Many of the functions in the MagickWand API are still missing, but over time more will be added. Pull requests are welcome.
Dependencies
- Rust stable
- ImageMagick (version 7.0.x to 7.1.x)
- Does not work with ImageMagick 6.x due to backward incompatible changes.
- FreeBSD:
sudo pkg install ImageMagick7
- Homebrew:
brew install imagemagick
- Linux may require building ImageMagick from source, see the
Dockerfile
for an example - Windows: download
*-dll
installer. Only MSVC version available. When installing, check the checkbox "Install development headers and libraries for C and C++".
- Clang (version 3.5 or higher)
- Or whatever version is dictated by rust-bindgen
- Windows requires MSVC toolchain
- Optionally
pkg-config
, to facilitate linking with ImageMagick. Or you can set linker parameters via environment variables.
Build and Test
Pretty simple for now.
$ cargo build
$ cargo test
Optionally you can set some environment variables before building:
IMAGE_MAGICK_DIR
- installation directory of ImageMagickIMAGE_MAGICK_LIB_DIRS
- list of lib directories split by:
IMAGE_MAGICK_INCLUDE_DIRS
- list of include directories split by:
IMAGE_MAGICK_LIBS
- list of the libs to link to
Build on Windows
On Windows you will need to launch build in Visual Studio Native Tools Command Prompt.
It can be found in Start menu -> Visual Studio < VERSION > -> Visual Studio Tools -> Windows Desktop Command Prompts.
Choose the architecture corresponding to architecture of your rust compiler.
This is required for the proper functioning of rust-bindgen
.
> set IMAGE_MAGICK_DIR=<path to ImageMagick installation directory>
> cargo build
> cargo test
Build Troubleshooting
QuantumRange
in module bindings
Error: cannot find value When attempting to build the library, you might see an error like this one:
error[E0425]: cannot find value `QuantumRange` in module `bindings`
--> C:\Users\charlie\.cargo\registry\src\github.com-1ecc6299db9ec823\magick_rust-0.9.0\src\wand\magick.rs:337:80
|
337 | if bindings::MagickSepiaToneImage(self.wand, threshold * bindings::QuantumRange) == bindings::MagickBooleanType::MagickTrue {
|
^^^^^^^^^^^^ not found in `bindings`
error: aborting due to previous error
See issue 40 on GitHub for some background. The issue seems to be that with HDRI disabled, rust-bindgen will not produce the bindings needed for the "quantum range" feature of ImageMagick (see issue 316). To work-around this issue, you can disable HDRI support in your Cargo.toml
file, like so:
magick_rust = { version = "0.15.0", features = ["disable-hdri"] }
Example Usage
MagickWand has some global state that needs to be initialized prior to using the library, but fortunately Rust makes handling this pretty easy. In the example below, we read in an image from a file and resize it to fit a square of 240 by 240 pixels, then convert the image to JPEG.
use magick_rust::{MagickWand, magick_wand_genesis};
use std::sync::Once;
// Used to make sure MagickWand is initialized exactly once. Note that we
// do not bother shutting down, we simply exit when we're done.
static START: Once = Once::new();
fn resize() -> Result<Vec<u8>, &'static str> {
START.call_once(|| {
magick_wand_genesis();
});
let wand = MagickWand::new();
try!(wand.read_image("kittens.jpg"));
wand.fit(240, 240);
wand.write_image_blob("jpeg")
}
Writing the image to a file rather than an in-memory blob is done by replacing the call to write_image_blob()
with write_image()
, which takes a string for the path to the file.
Frequent API Changes
Because rust-bindgen changes from time to time, and is very difficult to use for a library as large as ImageMagick, the API of this crate may experience dramatic mood swings. Typically this pain manifests itself in the way the enums are represented. I am deeply sorry for this pain. Hopefully someone smarter than me can fix it some day. Pull requests are welcome.
Contributing
There are still many missing functions, so if you find there is something you would like to see added to this library, feel free to file an issue. Even better, fork the repo, and write the thin wrapper necessary to expose the MagickWand function. For getters and setters this is often very easy, just add a row to the table in wand/magick.rs
, and it will work with no additional coding. Tests are optional, as this crate is basically a thin wrapper around code that is assumed to be thoroughly tested already. If you make a change that you want to contribute, please feel free to submit a pull request.
Docker
Docker can be used to build and test the code without affecting your development environment, which may have a different version of ImageMagick installed. The use of docker-compose
, as shown in the example below, is optional, but it makes the process very simple.
$ cd docker
$ docker-compose build --pull
$ docker-compose run magick-rust
$ cargo clean
$ cargo build
$ cargo test