[vtkusers] Problem VTK4 + python 2.2

Emmanuel Olart olart at theralys.com
Mon Jan 14 06:04:28 EST 2002


Hummm last problem,

it works, it displays the renderWindow but if I ever try to clik on it 
or to display something in it, my X server get killed ...

Emmanuel

Emmanuel Olart wrote:

> Right it also works for me when setting my PYTHONPATH and my 
> LD_LIBRARY_PATH to the path where i built VTK
>
> export PYTHONPATH=$VTKSRC/Wrapping/python:$VTKSRC/bin
> export LD_LIBRARY_PATH=$VTKSRC/bin
>
> but as prabbhu wrote, if my LD_LIBRARY_PATH points also to 
> /usr/local/lib/vtk it doesn t work anymore ...
>
> I think maybe the make install did something odd with the path?
>
> Souldn t the python wrappers be copied somewhere else ?
>
> Regards
>
> Emmanuel
>
> Prabhu Ramachandran wrote:
>
>>>>>>> "JP" == Jose Paulo Moitinho de Almeida 
>>>>>>> <moitinho at civil.ist.utl.pt> writes:
>>>>>>>
>>
>>
>>    JP>     def init_scalar_bar (self): "Sets up the default scalar
>>    JP> bar."  debug ("In LutHandler::init_scalar_bar ()") self.sc_bar
>>    JP> = vtkpython.vtkScalarBarActor () self.sc_bar.SetLookupTable
>>    JP> (self.lut)
>>
>>    JP> I got in the SetLookupTable command a: "ValueError: method
>>    JP> requires a VTK object (in init_scalar_bar)"
>>
>> Ahh, I remember this one.  I had this happen to me long back.  IIRC,
>> this happens when you have two copies of the VTK libraries accessible
>> in different places and when a module is somehow imported twice.  In
>> my situation I had built VTK with the libs in
>> /skratch/prabhu/vtk/cvs/VTK/lib and I had also copied those libraries
>> to another directory to make some binaries.  I had my LD_LIBRARY_PATH
>> set to the directory /skratch/prabhu/vtk/cvs/VTK/lib and even when I
>> unset it and set it to the current directory (where I had copied the
>> libs) I would get this ValueError exception.  What I finally needed to
>> do was to change the name of the build directory from lib to lib1 (I
>> just moved the lib dir to lib1) and things worked.  I think the
>> problem is because the libvtk modules are being imported twice.  It
>> was Gordon McMillan who suggested this possibility to me.
>>
>> prabhu
>> _______________________________________________
>> This is the private VTK discussion list. Please keep messages 
>> on-topic. Check the FAQ at: <http://public.kitware.com/cgi-bin/vtkfaq>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/vtkusers
>>
>>
>
>
>
> _______________________________________________
> This is the private VTK discussion list. Please keep messages 
> on-topic. Check the FAQ at: <http://public.kitware.com/cgi-bin/vtkfaq>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers
>
>






More information about the vtkusers mailing list