PythonMagick on OS X

pythonmagick_osx.md

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.

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'.

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

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.

@bwagner
Can you help me insolving the above error.

PythonMagick is working on MacOS Big Sur 11.2.3 with Homebrew and python 3.9
here are my installation steps. After having already installed homebrew;

1. Install dependencies, including the llvm clang compiler which is required to use OpenMP, since XCode's clang doesn't support it.
   brew install python3 boost boost-python3 imagemagick llvm
   This will take a while.

2. Get source
   git clone https://github.com/ImageMagick/PythonMagick
cd PythonMagick

3. Edit configure to correctly locate boost-python by replacing two instances of ax_python_lib=boost_python with ax_python_lib=boost_python39. My entries appear on lines 17992 and 18414. Your exact version of boost_python may vary in future, so check ls -l /usr/local/lib/libboost_python* first to see).

4. Set BOOST_ROOT (your version may vary)
   export BOOST_ROOT=/usr/local/Cellar/boost/1.75.0_2

5. Run the configure script, telling it explicitly where to find the correct compilers (llvm clang) and which python version and boost libraries to use. Your versions for boost and python may vary.
   ./configure CC=/usr/local/opt/llvm/bin/clang CXX=/usr/local/opt/llvm/bin/clang++ PYTHON=python3.9 CPPFLAGS="-I/usr/local/Cellar/boost/1.75.0_2/include" LDFLAGS="-L/usr/local/lib"

6. If the above works, then all that is required now is make; make install

If the linking step fails during make with an error such as ld: library not found for -l-L/usr/local/Cellar/imagemagick... then this indicates that libboost_python wasn't found by the configure script; the hanging -l is meant to point to -lboost-python39 or similar.

Similarly, if you get 'symbol not found' errors at runtime in python, this also indicates a failure to link to libboost-python. Make sure you've run brew install boost-python3 and use brew doctor to check for any broken links. Also make sure you're not linking against any "legacy" libraries, especially if like me you upgraded to Big Sur over the top of Mojave or Catalina. You might want to wipe away libboost_python and completely reinstall it if this happens.

7. Go to anywhere other than the PythonMagick directory or its parent directory & run python3 -c 'import PythonMagick'. If successful, there should be no output / errors.