Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
PythonMagick on OS X

Installing PythonMagick on OS X

  1. brew install boost - will take a lot of time and make your Mac hot
  2. brew install --with-magick-plus-plus imagemagick
  3. cd <path_to_PythonMagick_source>
  4. ./configure --with-boost=<path_to_boost_root>
  5. make
  6. make install
  7. python -c "import PythonMagick"

If PythonMagick build fails saying that it couldn't find -lboost_python navigate to <path_to_boost_root>/lib/, ln -s libboost_python-mt.dylib libboost_python.dylib and run make again.

Tested on 10.6.8 with Python 2.6.7 (custom build). Should work with Lion running stock 2.7.

NOTE: Looks like I was too quick to call it done. The module imports but raises exceptions when used. Bummer.

@Ringil

This comment has been minimized.

Copy link

commented Jun 10, 2012

Did you ever figure out how to solve the import problem?

@tomekwojcik

This comment has been minimized.

Copy link
Owner Author

commented Jun 10, 2012

@Ringil

This comment has been minimized.

Copy link

commented Jun 11, 2012

I solved this problem by copying from where make install installed PythonMagick /usr/local/lib/python2.7/site-packages/PythonMagick to where Python actually looks on a OS X Lion, /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/

@nfglynn

This comment has been minimized.

Copy link

commented Jul 5, 2012

Just a quick note for anyone checking this in future, after successfully building PythonMagick on Mac OS X Lion I was getting:

>>> import PythonMagick
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "PythonMagick/__init__.py", line 1, in <module>
from . import _PythonMagick
ImportError: cannot import name _PythonMagick

This can be fixed by changing the first line of __init__.py in PythonMagick (Usually to be found in site-packages, in my case /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PythonMagick) from:

from . import _PythonMagick

to

import _PythonMagick
@slawek87

This comment has been minimized.

Copy link

commented Jul 17, 2014

is there any howto about installing PythonMagick on mac os x? It's annoying problem.

@kenessajr

This comment has been minimized.

Copy link

commented Jul 4, 2015

can find ./configure file .

RemyMuhire@Muhires-MBP:~$ cd /usr/local/Cellar/imagemagick/6.8.9-8
RemyMuhire@Muhires-MBP:/usr/local/Cellar/imagemagick/6.8.9-8$ ./configure --with-boost=/usr/local/Cellar/boost/1.56.0
-bash: ./configure: No such file or directory
RemyMuhire@Muhires-MBP:/usr/local/Cellar/imagemagick/6.8.9-8$

@DWishR

This comment has been minimized.

Copy link

commented Nov 6, 2015

I got it working. Note that in the future boost/1.59.0 will change to something else.
Download PythonMagick-0.9.12 and unzip/untar/unwhatevs

$ brew install --with-magick-plus-plus imagemagick
$ brew install boost --with-python
$ brew install boost-python

$ cd ~/Downloads/PythonMagick-0.9.12
$ BOOST_ROOT=/usr/local/Cellar/boost/1.59.0/
$ ./configure

Now you need to edit Makefile and pythonmagick_src/Makefile to include the boost library. You want to find two lines, one that starts with DEFAULT_INCLUDES and the other with LDFLAGS. Add boost paths to the end of those lines so they look something like this:
DEFAULT_INCLUDES = -I. -I$(top_builddir)/config -I/usr/local/Cellar/boost/1.59.0/include
LDFLAGS = -L/usr/local/Cellar/boost-python/1.59.0/lib

$ make
$ make install

Edit __init__.py in the PythonMagick package folder, I found it at /usr/local/lib/python2.7/site-packages/PythonMagick. If you can't find the path, it should be at the end of the output of make install, on a line like: /bin/sh ./libtool --mode=install /usr/bin/install -c _PythonMagick.la '/usr/local/lib/python2.7/site-packages/PythonMagick'.

You want to change the first line of __init__.py from:

from . import _PythonMagick

to:

import _PythonMagick

And that should do it!

@rgvasquez

This comment has been minimized.

Copy link

commented Jul 8, 2016

@DWishR I was able to get through the instructions, but it still gives me "No module named PythonMagick" I noticed that even though I edited init.py, the corresponding init.pyc and init.pyo does not get rebuild when I import PythonMagick.

@corey-cole

This comment has been minimized.

Copy link

commented Aug 31, 2016

@DWishR Just followed your instructions to a tee (correcting for new versions) and it worked perfectly. Thanks!

@nazikus

This comment has been minimized.

Copy link

commented Nov 20, 2016

@DWishR as of today, your solution still works, thanks.
PythonMagick-0.9.15
boost-1.62.0
boost-python-1.62.0

note: brew install --with-magick-plus-plus imagemagick gives warning
Warning: imagemagick: this formula has no --with-magick-plus-plus option so it will be ignored!
but nevertheless it worked, thanks.

@duyvk

This comment has been minimized.

Copy link

commented Dec 27, 2016

i got this error when running "make"

 Making all in helpers_src

  CXX      libhelper_la-Blob.lo

  CXXLD    libhelper.la

  CXXLD    _PythonMagick.la

clang: warning: argument unused during compilation: '-pthread'

ld: library not found for -l-L/usr/local/Cellar/imagemagick/6.9.7-0/lib

clang: error: linker command failed with exit code 1 (use -v to see invocation)

make[1]: *** [_PythonMagick.la] Error 1

make: *** [all-recursive] Error 1

Do you guys know what may cause the problem ?
Thanks !

@krishnakt031990

This comment has been minimized.

Copy link

commented Apr 10, 2017

CXX libpymagick_la-_Image.lo
_Image.cpp:400:92: error: no member named 'alphaColor' in 'Magick::Image'
.def("alphaColor", (void (Magick::Image::)(const Magick::Color&) )&Magick::Image::alphaColor)
~~~~~~~~~~~~~~~^
_Image.cpp:401:86: error: no member named 'alphaColor' in 'Magick::Image'
.def("alphaColor", (Magick::Color (Magick::Image::
)() const)&Magick::Image::alphaColor)
~~~~~~~~~~~~~~~^
2 errors generated.
make[1]: *** [libpymagick_la-_Image.lo] Error 1
make: *** [all-recursive] Error 1

Anyone getting these errors?

@anasamoudi

This comment has been minimized.

Copy link

commented Apr 10, 2017

@krishnakt031990 Yes I'm getting the same error.

Managed to solve it by downloading this version http://www.imagemagick.org/download/python/PythonMagick-0.9.16.tar.bz2

@JonniePerkgit

This comment has been minimized.

Copy link

commented Apr 12, 2017

@krishnakt031990 same error for me. @anasamoudi I tried your solution and it didn't work.... Any other ideas?

Is there an issue with the new release? I can't find anything on yee old Google about this...

OS: macOS 10.12.4
Python: 2.7.13
Trying to install: PythonMagick-0.9.16 (I've also tried 0.9.15 which produced the same error)

@Jasper912

This comment has been minimized.

Copy link

commented Jul 5, 2017

@duyvk Hey, I'm getting this error too

Making all in helpers_src
  CXX      libhelper_la-Blob.lo
  CXXLD    libhelper.la
  CXXLD    _PythonMagick.la
clang: warning: argument unused during compilation: '-pthread' [-Wunused-command-line-argument]
ld: library not found for -l-L/usr/local/Cellar/imagemagick@6/6.9.8-10/lib
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [_PythonMagick.la] Error 1
make: *** [all-recursive] Error 1

Have you solved the problem yet?
Thanks!

@SylvainGuieu

This comment has been minimized.

Copy link

commented Aug 4, 2017

@Jasper912 @duyvk
I had the same problem the BOOST_PYTHON_LIB was empty in the MakeFile. I just removed the -l{BOOST_PYTHON_LIB} when it appear in the MakeFile and it compile.

@djorlando24

This comment has been minimized.

Copy link

commented Dec 27, 2017

Due to changes in the ImageMagick API for version 7 and later, as of PythonMagick-0.9.18 there are some broken hooks that will raise Symbol Not Found errors when attempting to import the dynamic library, and possibly a KeyError('cacheThreshold') when attempting to import PythonMagick. In addition to the above steps (using homebrew to install ImageMagick, boost, boost-python etc). You may also need to apply the following changes. Here I have done a 'git diff' on my version (working on MacOS 10.12.6 with ImageMagick 7.0.5) against the current master branch as of late Dec 2017.

diff --git a/../PythonMagick-master/pythonmagick_src/_Image.cpp b/./pythonmagick_src/_Image.cpp
index 8791c74..5c26cfa 100644
--- a/../PythonMagick-master/pythonmagick_src/_Image.cpp
+++ b/./pythonmagick_src/_Image.cpp
@@ -490,8 +490,8 @@ void Export_pyste_src_Image()
         .def("modifyImage", &Magick::Image::modifyImage)
 #if MagickLibVersion < 0x700
         .def("throwImageException", &Magick::Image::throwImageException)
-#endif
         .staticmethod("cacheThreshold")
+#endif
         .def( self == self )
         .def( self != self )
         .def( self > self )
diff --git a/../PythonMagick-master/pythonmagick_src/_main.cpp b/./pythonmagick_src/_main.cpp
index 449f0b1..a7d3cce 100644
--- a/../PythonMagick-master/pythonmagick_src/_main.cpp
+++ b/./pythonmagick_src/_main.cpp
@@ -30,7 +30,7 @@ void Export_pyste_src_PathArcAbs();
 void Export_pyste_src_Image();
 void Export_pyste_src_GravityType();
 void Export_pyste_src_Geometry();
-void Export_pyste_src_FilterTypes();
+void Export_pyste_src_FilterType();
 void Export_pyste_src_Exception();
 void Export_pyste_src_DrawableViewbox();
 void Export_pyste_src_DrawableTranslation();
@@ -62,7 +62,7 @@ void Export_pyste_src_DrawablePointSize();
 void Export_pyste_src_DrawablePoint();
 void Export_pyste_src_DrawablePath();
 void Export_pyste_src_DrawableMiterLimit();
-void Export_pyste_src_DrawableMatte();
+void Export_pyste_src_DrawableAlpha();
 void Export_pyste_src_DrawableLine();
 void Export_pyste_src_DrawableGravity();
 void Export_pyste_src_DrawableFont();
@@ -70,8 +70,8 @@ void Export_pyste_src_DrawableFillRule();
 void Export_pyste_src_DrawableFillOpacity();
 void Export_pyste_src_DrawableFillColor();
 void Export_pyste_src_DrawableEllipse();
-void Export_pyste_src_DrawableDashOffset();
-void Export_pyste_src_DrawableDashArray();
+void Export_pyste_src_DrawableStrokeDashOffset();
+void Export_pyste_src_DrawableStrokeDashArray();
 void Export_pyste_src_DrawableCompositeImage();
 void Export_pyste_src_DrawableColor();
 void Export_pyste_src_DrawableClipPath();
@@ -119,7 +119,7 @@ BOOST_PYTHON_MODULE(_PythonMagick)
     Export_pyste_src_Image();
     Export_pyste_src_GravityType();
     Export_pyste_src_Geometry();
-    Export_pyste_src_FilterTypes();
+    Export_pyste_src_FilterType();
     Export_pyste_src_Exception();
     Export_pyste_src_DrawableViewbox();
     Export_pyste_src_DrawableTranslation();
@@ -151,7 +151,7 @@ BOOST_PYTHON_MODULE(_PythonMagick)
     Export_pyste_src_DrawablePoint();
     Export_pyste_src_DrawablePath();
     Export_pyste_src_DrawableMiterLimit();
-    Export_pyste_src_DrawableMatte();
+    Export_pyste_src_DrawableAlpha();
     Export_pyste_src_DrawableLine();
     Export_pyste_src_DrawableGravity();
     Export_pyste_src_DrawableFont();
@@ -159,8 +159,8 @@ BOOST_PYTHON_MODULE(_PythonMagick)
     Export_pyste_src_DrawableFillOpacity();
     Export_pyste_src_DrawableFillColor();
     Export_pyste_src_DrawableEllipse();
-    Export_pyste_src_DrawableDashOffset();
-    Export_pyste_src_DrawableDashArray();
+    Export_pyste_src_DrawableStrokeDashOffset();
+    Export_pyste_src_DrawableStrokeDashArray();
     Export_pyste_src_DrawableCompositeImage();
     Export_pyste_src_DrawableColor();
     Export_pyste_src_DrawableClipPath();
@djorlando24

This comment has been minimized.

Copy link

commented Dec 27, 2017

Following above, you'll need to modify __init__.py to point to the correct functions as well.

diff --git a/../PythonMagick-master/PythonMagick/__init__.py b/./PythonMagick/__init__.py
index 6750c2e..61ba8d4 100644
--- a/../PythonMagick-master/PythonMagick/__init__.py
+++ b/./PythonMagick/__init__.py
@@ -51,10 +51,10 @@ class DrawableColor(_PythonMagick.DrawableColor):
 class DrawableCompositeImage(_PythonMagick.DrawableCompositeImage):
    pass
 
-class DrawableDashArray(_PythonMagick.DrawableDashArray):
+class DrawableStrokeDashArray(_PythonMagick.DrawableStrokeDashArray):
    pass
 
-class DrawableDashOffset(_PythonMagick.DrawableDashOffset):
+class DrawableStrokeDashOffset(_PythonMagick.DrawableStrokeDashOffset):
    pass
 
 class DrawableEllipse(_PythonMagick.DrawableEllipse):
@@ -78,7 +78,7 @@ class DrawableGravity(_PythonMagick.DrawableGravity):
 class DrawableLine(_PythonMagick.DrawableLine):
    pass
 
-class DrawableMatte(_PythonMagick.DrawableMatte):
+class DrawableAlpha(_PythonMagick.DrawableAlpha):
    pass
 
 class DrawableMiterLimit(_PythonMagick.DrawableMiterLimit):
@@ -174,7 +174,7 @@ class DrawableViewbox(_PythonMagick.DrawableViewbox):
 class Exception(_PythonMagick.Exception):
    pass
 
-class FilterTypes(_PythonMagick.FilterTypes):
+class FilterType(_PythonMagick.FilterType):
    pass
 
 class Geometry(_PythonMagick.Geometry):
@bwagner

This comment has been minimized.

Copy link

commented Dec 12, 2018

This version (PythonMagick-0.9.18) seems to fix the above errors:
I can do:

./configure
make
make install

on 10.13.6 (High Sierra), Python 2.7.15, resulting in output below. However, if I do python -c "import PythonMagick", I get:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "PythonMagick/__init__.py", line 1, in <module>
    from . import _PythonMagick
ImportError: cannot import name _PythonMagick

Output for make install:

Making install in pythonmagick_src
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
Making install in helpers_src
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
 /usr/local/bin/gmkdir -p '/usr/local/lib/python2.7/site-packages/PythonMagick'
 /bin/sh ./libtool   --mode=install /usr/local/bin/ginstall -c   _PythonMagick.la '/usr/local/lib/python2.7/site-packages/PythonMagick'
libtool: install: /usr/local/bin/ginstall -c .libs/_PythonMagick.so /usr/local/lib/python2.7/site-packages/PythonMagick/_PythonMagick.so
libtool: install: /usr/local/bin/ginstall -c .libs/_PythonMagick.lai /usr/local/lib/python2.7/site-packages/PythonMagick/_PythonMagick.la
libtool: install: /usr/local/bin/ginstall -c .libs/_PythonMagick.a /usr/local/lib/python2.7/site-packages/PythonMagick/_PythonMagick.a
libtool: install: chmod 644 /usr/local/lib/python2.7/site-packages/PythonMagick/_PythonMagick.a
libtool: install: ranlib /usr/local/lib/python2.7/site-packages/PythonMagick/_PythonMagick.a
 /usr/local/bin/gmkdir -p '/usr/local/lib/python2.7/site-packages/PythonMagick'
 /usr/local/bin/ginstall -c -m 644 PythonMagick/__init__.py '/usr/local/lib/python2.7/site-packages/PythonMagick'
Byte-compiling python modules...
__init__.py
Byte-compiling python modules (optimized versions) ...
__init__.py
make[2]: Nothing to be done for `install-data-am'.
@dwrama50

This comment has been minimized.

Copy link

commented Apr 9, 2019

how to setup the pythonmagick in my mac? below is my python site packages path: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages

@dwrama50

This comment has been minimized.

Copy link

commented Apr 9, 2019

MacbookPro:PythonMagick-0.9.192 ramareddy$ ./configure LIBS="-L/Library/Frameworks/Python.framework/Versions/2.7/lib" PYTHON_EXTRA_LDFLAGS='-u _PyMac_Error /Library/Frameworks/Python.framework/Versions/2.7/Python' LDFLAGS="-L/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7"
checking whether build environment is sane... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for a thread-safe mkdir -p... config/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-apple-darwin17.7.0
checking host system type... x86_64-apple-darwin17.7.0
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /Library/Developer/CommandLineTools/usr/bin/ld
checking if the linker (/Library/Developer/CommandLineTools/usr/bin/ld) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 196608
checking how to convert x86_64-apple-darwin17.7.0 file names to x86_64-apple-darwin17.7.0 format... func_convert_file_noop
checking how to convert x86_64-apple-darwin17.7.0 file names to toolchain format... func_convert_file_noop
checking for /Library/Developer/CommandLineTools/usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @file support... no
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for lipo... lipo
checking for otool... otool
checking for otool64... no
checking for -single_module linker flag... yes
checking for -exported_symbols_list linker flag... yes
checking for -force_load linker flag... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking for gcc option to produce PIC... -fno-common -DPIC
checking if gcc PIC flag -fno-common -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/Library/Developer/CommandLineTools/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin17.7.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /Library/Developer/CommandLineTools/usr/bin/ld
checking if the linker (/Library/Developer/CommandLineTools/usr/bin/ld) is GNU ld... no
checking whether the g++ linker (/Library/Developer/CommandLineTools/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fno-common -DPIC
checking if g++ PIC flag -fno-common -DPIC works... yes
checking if g++ static flag -static works... no
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/Library/Developer/CommandLineTools/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin17.7.0 dyld
checking how to hardcode library paths into programs... immediate
checking for pkg-config... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking for python with minimal version... 2.4
checking for a Python interpreter with version >= 2.4... python
checking for python... /Library/Frameworks/Python.framework/Versions/2.7/bin/python
checking for python version... 2.7
checking for python platform... darwin
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for python2.7... (cached) /Library/Frameworks/Python.framework/Versions/2.7/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for a version of Python >= '2.4'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
checking for Python library path... -L/Library/Frameworks/Python.framework/Versions/2.7/lib -lpython2.7
checking for Python site-packages path... /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
checking python extra libraries... -u _PyMac_Error /Library/Frameworks/Python.framework/Versions/2.7/Python
checking python extra linking flags... -u _PyMac_Error Python.framework/Versions/2.7/Python
checking consistency of all components of python development environment... no
configure: error: in `/Users/ramareddy/Downloads/PythonMagick-0.9.192':
configure: error:
Could not link test program to Python. Maybe the main Python library has been
installed in some non-standard library path. If so, pass it to configure,
via the LIBS environment variable.
Example: ./configure LIBS="-L/usr/non-standard-path/python/lib"

ERROR!
You probably have to install the development version of the Python package
for your distribution. The exact name of this package varies among them.

@dwrama50

This comment has been minimized.

Copy link

commented Apr 10, 2019

@bwagner
Can you help me insolving the above error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.