Has anyone installed pycairo 1.10 on the mac using the new waf build? Its failing on can't find python headers.
I think waf is seriously broken for Mac OS X :(
Here's how it worked for me. After python waf configure
failed to find Python.h, I looked through the config.log file located in build_directory and found out that the true cause of failure was incompatible architecture. The waf script tries to build a simple source file with CPython calls in it using i386 architecture. It fails to do so, because my python is built for the x86_64 architecture.
I guess, you could rebuild python as a universal binary, I haven't tried that. It is possible, however, to build pycairo using the x86_64 architecture. Here's how.
My setup:
$ python --version
Python 2.7.2
$ type python
python is /usr/local/bin/python
$ file /usr/local/bin/python
/usr/local/bin/python: Mach-O 64-bit executable x86_64
$ brew --version
0.8
Importrant: my python version is built for the x86_64
architecture. Make sure it is also the case for you before performing the steps described below.
brew stands for homebrew. You must use it instead of fink or MacPorts in order for the following steps to work for you.
Now, to install cairo and pycairo I do the following:
brew install cairo
(version 1.10.2 as of today)
Get pycairo source for python 2.x (if you get a snapshot, it is named py2cairo, whereas pycairo now requires python 3.x). I used the source from master branch (commit f3435910d8f5365b45ebd4216f4043383c9e3e19)
Open wscript
in your editor of choice, locate the line env = ctx.env
in the function configure
and add the following line below it
env.append_unique('CFLAGS', ['-arch', 'x86_64'])
Save the file
Run these commands in your terminal:
export CC=/usr/bin/gcc
export PKG_CONFIG_PATH=/usr/local/Cellar/cairo/1.10.2/lib/pkgconfig/
Important: the latter path will only work for you if you installed cairo via homebrew
Then run the waf commands described in the pycairo's INSTALL file:
python waf configure
python waf build
python waf install
This should do it. If it doesn't work for you, I think it's better to raise the topic on the pycairo mailing list (if it has one).