#include <Python.h> becomes #include <python2.5/Python.h> for OS X
|Reported by:||jmonk||Owned by:||jmonk|
|Keywords:||Cc:||Andy Buckley, hoeth, Frank Siegert|
The system python libraries on OS X seem to use some fancy framework setup in /System/Library/Frameworks/Python?.framework/Versions/2.5/include/python2.5/. I think the point of the framework bundle structure is to allow you to switch versions with ease, so it would seem to make sense that it forces you to specify a version. Since you can swap the framework without recompiling the dependencies it can't rely on the current version.
Googling around this a bit it seems like even on Linux some people use
#include <python/Python.h>. I guess the Rivet build system already adds places like /usr/local/include/python - maybe it shouldn't?