On 16-Dec-08, at 3:13 PM, Dav Clark wrote:
For completeness / clarity, you simply CAN'T build VTK bindings from the stock sources targeting the system python if you have ANY Frameworks installed. You can modify some of the build scripts and get a successful install, however. I would not be surprised if this happened in other complex libs.
Even worse, once it's built against one or the other python build (at least when I built it) it dumps it's python modules in /usr/local/lib/ python2.5/site-packages instead of the proper location of site- packages. It basically makes the false assumption that python and vtk are installed under the same prefix, even though it's using a python that's not even *symlinked* from /usr/local to actually get headers/do the build.
There's a (universal) binary I built against VTK 5.0.4 and Python.org Python 2.5.2, if anyone's interested (mainly for the purposes of Googlers who might find this thread). It goes to the trouble of putting the python wrappers in the right place (under /Library/ Frameworks/Python.framework/Versions/2.5):
https://svn.enthought.com/enthought/attachment/wiki/MayaVi/VTK504UB.dmg - DWF _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
