[vtkusers] Build failure for vtk on os x Panther with python

[Frederick Grim]

On Mar 17, 2004, at 4:18 AM, Sander Niemeijer wrote:

> I think you stumbled upon the same thing I did once. It is a CMake 
> thing.
> I used CMake 1.8.1 and if you look at the file 
> cmake-1.8.1/Modules/FindPythonLibs.cmake file you see there are some 
> special rules for the Apple platform. The weird thing (and I have 
> absolutely no idea why they do this!) is that they check whether your 
> PYTHON_INCLUDE_PATH matches the string 'Python.framework' (which it 
> does in your case) and if this is the case CMake sets the 
> PYTHON_LIBRARY to "". So your PYTHON_LIBRARY setting actually gets 
> deleted!!!!!
> The trick I did is to make a symbolic link (that doesn't include the 
> name 'Python.framework' in its path) somewhere, point this to the 
> Python include directory and then provide the location of the symbolic 
> link to PYTHON_INCLUDE_PATH.
>
This was exactly the problem...You are the man.
	Fred


> Regards,
> Sander
>
> On woensdag, maa 17, 2004, at 03:11 Europe/Amsterdam, Frederick Grim 
> wrote:
>
>> Howdy all,
>> 	As I get the chance I make a (generally weekly) attempt to build vtk 
>> with python bindings.
>> It never works. So I wait a week, lookup some documentation, and try 
>> again.  Well I have surrendered
>> Everytime I build vtk with the python bindings (if I can't have em I 
>> can't use vtk as python is my prototyping
>> tool) I see a failure like:
>>
>> Building shared library 
>> /Users/hal9000/VTK/bin/libvtkCommonPythonD.dylib...
>> ld: Undefined symbols:
>> _PyErr_Clear
>> _PyFloat_FromDouble
>> _PyInt_FromLong
>> _PyString_FromString
>> __Py_NoneStruct
>> _PyErr_SetString
>> _PyExc_TypeError
>> _Py_BuildValue
>> _PyArg_ParseTuple
>> _PyCallable_Check
>> _PyExc_ValueError
>> _PyString_FromStringAndSize
>> _PyArg_ParseTupleAndKeywords
>> _PyArg_VaParse
>> _PyCFunction_NewEx
>> _PyCFunction_Type
>> _PyDict_DelItem
>> _PyDict_DelItemString
>> _PyDict_GetItem
>> _PyDict_GetItemString
>> _PyDict_New
>> _PyDict_SetItem
>> _PyDict_SetItemString
>> _PyDict_Type
>> _PyErr_ExceptionMatches
>> _PyErr_Print
>> _PyEval_CallObjectWithKeywords
>> _PyEval_GetGlobals
>> _PyExc_AttributeError
>> _PyExc_KeyboardInterrupt
>> _PyExc_RuntimeError
>> _PyFloat_AsDouble
>> _PyInt_AsLong
>> _PyList_New
>> _PyList_SetItem
>> _PyList_Sort
>> _PyMethod_New
>> _PyObject_Free
>> _PyObject_GetAttrString
>> _PySequence_GetItem
>> _PySequence_SetItem
>> _PyString_AsString
>> _PyString_InternFromString
>> _PyString_Type
>> _PyTuple_GetItem
>> _PyTuple_GetSlice
>> _PyTuple_New
>> _PyTuple_Size
>> _PyTuple_Type
>> _PyType_IsSubtype
>> _PyType_Type
>> _Py_AtExit
>> _Py_Exit
>> __PyObject_New
>> __PyString_Resize
>> /usr/bin/libtool: internal link edit command failed
>> make[3]: *** [/Users/hal9000/VTK/bin/libvtkCommonPythonD.dylib] Error 
>> 1
>> make[2]: *** [default_target] Error 2
>> make[1]: *** [default_target_Common] Error 2
>> make: *** [default_target] Error 2
>>
>> My CMakeCache.txt is attached.  What am I doing wrong here?
>>
>> 	Thanks
>> 	Fred<CMakeCache.txt>
>