[Insight-users] WrapITK instal troubles

[Vincent Page]

hi,

and thanks for the help.
A part of my problems came, as you noticed from
my old CableSwig install.

so now, I just have
LD_LIBRARY_PATH set to /usr/local/lib/InsightToolkit

And now, when I
./test_regionGrow.py

I have :
Traceback (most recent call last):
  File "./test_regionGrow.py", line 7, in ?
    import itk
  File "/usr/local/lib/InsightToolkit/WrapITK/Python/itk.py", line 19, in ?
    itkBase.LoadModule(module, globals())
  File "/usr/local/lib/InsightToolkit/WrapITK/Python/itkBase.py", line 
61, in LoadModule
    if not swigModuleName in sys.modules: module = 
loader.load(swigModuleName)
  File "/usr/local/lib/InsightToolkit/WrapITK/Python/itkBase.py", line 
162, in load
    return imp.load_module(name, fp, pathname, description)
  File 
"/usr/local/lib/InsightToolkit/WrapITK/Python-SWIG/ITKTclSupportPython.py", 
line 5, in ?
    import _ITKTclSupportPython
ImportError: 
/usr/local/lib/InsightToolkit/WrapITK/Python-SWIG/_ITKTclSupportPython.so: 
undefined symbol: Tcl_GlobalEval

which I guess, is due to the support of Tcl.
I might suppress it from WrapITK as well but I thought it might be 
useful to someone
on the server.

Is it an easy thing to fix ?
If not, am I right to think that this could be fixed by
suppressing the Tcl support in WrapITK ?

Vincent.






Zachary Pincus a écrit :

>
>>    import _VXLNumericsPython
>> ImportError: libitkvnl.so: cannot open shared object file: No such  
>> file or directory
>> --------------------------------------------------
>>
>> I can find libitkvnl.so in
>> /usr/local/lib/InsightToolkit/libitkvnl.so
>>
>> I played a little with some environnement variable
>> so that now I have
>> PYTHONPATH=/usr/local/lib/InsightToolkit/python/:/usr/local/lib/ 
>> InsightToolkit/
>> LD_LIBRARY_PATH=/usr/local/lib/InsightToolkit/WrapITK/Python-SWIG
>>
>> Someone (Gaetan ) ?
>
>
> /usr/local/lib/InsightToolkit needs to be on the LD_LIBRARY_PATH, not  
> the PYTHONPATH.
> The files in that directory are the ITK libraries that the loader  
> needs to find, not Python extensions. Since ITK doesn't put them in a  
> "normal" place (e.g. /usr/local/lib), you need to explicitly tell the  
> loader where to find them.
>
>  Also, the first part of the PYTHONPATH should point to:
> /usr/local/lib/InsightToolkit/WrapITK/Python/
> not
> /usr/local/lib/InsightToolkit/python/
> The former is the WrapITK directory, and the latter is the python  
> directory for the old ITK wrappers.
>