To see why this extension failed to compile, please check the mkmf.log which can be found here: Check the mkmf.log file for more details. Can't find MagickWand.h.Ĭould not create Makefile due to some reason, probably lack of necessary current directory: /home/kb10uy/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/bundler/gems/rmagick-42aa8ce34f61/ext/RMagick > ImageMagick 7 instead uses MagickCore/ and MagickWand/ respectively.

Prior versions of ImageMagick (4-6) reference the ImageMagick header files as magick/ and wand/. ImageMagick: Porting to ImageMagick Version 7 Header Files Probably #254 is related with this problem.

Once installed, we can set up a pre-built environment:Īs ImageMagick renewed the prefix of its header files at version 7, I can't build RMagick with ImageMagick-7.0.2. If you don't already have Vagrant installed, you can download and install it from here. Steps to get up and running with a passing build are as follows: 1) set up the Vagrant environment In order to minimize issues on your local machine, we recommend that you make use of a Vagrant installation. Information about reporting problems and getting help for ImageMagick is available at the ImageMagick website or the ImageMagick Forum. However, We can't help with Ruby installation and configuration or ImageMagick installation and configuration. Please report bugs in RMagick, its documentation, or its installation programs via the bug tracker on the RMagick issues page.

These programs are not installed in the RMagick documentation tree. You can find more sample RMagick programs in the /examples directory. It's safe to install a new release of RMagick over an earlier release. If you upgrade to a newer release of ImageMagick, make sure you're using a release of RMagick that supports that release.

R imagemagick r mac os