MantisBT - ParaView
View Issue Details
0014168ParaView(No Category)public2013-07-12 04:022014-02-27 10:20
Atri 
Utkarsh Ayachit 
normalminorhave not tried
closedno change required 
4.0 
4.1 
TBD
incorrect functionality
0014168: vtk python modules installed in wrong location
This is exactly the same problem that was reported in issue 12694 and was fixed with version 3.12. However, it seems to have resurfaced now with version 4.0.1. While trying to upgrade openSUSE's paraview package to version 4.0.1, I see that the installation script tries to install vtk's python modules in
/usr/bin/Python/vtk/
instead of in
/usr/lib(64)/paraview/

Version 3.98.x used to build just fine on the same version of openSUSE. Please have a look at the spec file and let me know if I am doing something wrong that is triggering this issue. The spec file is here
https://build.opensuse.org/package/view_file/home:badshah400:branches:science/paraview?expand=1&file=paraview.spec [^]

Thank you.
No tags attached.
Issue History
2013-07-12 04:02AtriNew Issue
2013-07-29 23:22Orion PoplawskiNote Added: 0031364
2013-08-11 17:28AtriNote Added: 0031431
2013-08-12 16:43Orion PoplawskiNote Added: 0031439
2014-02-24 10:57Utkarsh AyachitNote Added: 0032392
2014-02-24 11:07Orion PoplawskiNote Added: 0032395
2014-02-24 12:08Utkarsh AyachitNote Added: 0032396
2014-02-24 12:08Utkarsh AyachitStatusbacklog => gatekeeper review
2014-02-24 12:08Utkarsh AyachitFixed in Version => 4.1
2014-02-24 12:08Utkarsh AyachitResolutionopen => no change required
2014-02-24 12:08Utkarsh AyachitAssigned To => Utkarsh Ayachit
2014-02-24 12:08Utkarsh AyachitStatusgatekeeper review => customer review
2014-02-26 00:08AtriNote Added: 0032411
2014-02-27 10:20Utkarsh AyachitStatuscustomer review => closed

Notes
(0031364)
Orion Poplawski   
2013-07-29 23:22   
I'm running into the same issue trying to update the Fedora paraview package. VTK_PYTHON_SETUP_ARGS doesn't seem to be available. And -DVTK_INSTALL_PYTHON_USING_CMAKE:BOOL=OFF doesn't appear to help.
(0031431)
Atri   
2013-08-11 17:28   
I finally patched the CMakeLists file as follows. This gets paraview building again, although I do not know if this is the right thing to do or not...


Index: ParaView-v4.0.1-source/CMakeLists.txt
===================================================================
--- ParaView-v4.0.1-source.orig/CMakeLists.txt
+++ ParaView-v4.0.1-source/CMakeLists.txt
@@ -176,7 +176,7 @@ set (VTK_INSTALL_NO_QT_PLUGIN TRUE)
 
 # ParaView install the vtk python modules specifically to appropriate locations.
 set (VTK_INSTALL_NO_PYTHON TRUE)
-set (VTK_INSTALL_PYTHON_USING_CMAKE TRUE)
+set (VTK_INSTALL_PYTHON_USING_CMAKE FALSE)
 
 # for temporary backwards compatibility.
 set (PV_INSTALL_BIN_DIR ${VTK_INSTALL_RUNTIME_DIR})
(0031439)
Orion Poplawski   
2013-08-12 16:43   
So that's why setting on the command line had no effect! Works for me too.
(0032392)
Utkarsh Ayachit   
2014-02-24 10:57   
Guys, has anyone tried this withg 4.1? The Python installation rules were updated for 4.1. Please let me know if the problem persists with 4.1 and we can track it down.

Thanks for all your help.
(0032395)
Orion Poplawski   
2014-02-24 11:07   
4.1 appears to honor VTK_INSTALL_PYTHON_MODULE_DIR just fine and works for me. Thanks.
(0032396)
Utkarsh Ayachit   
2014-02-24 12:08   
Great! I'll close this one then. Atri, please feel free to reopen if you run into problems. Thanks.
(0032411)
Atri   
2014-02-26 00:08   
Thank you very much. VTK_INSTALL_PYTHON_MODULE_DIR works just fine for me too with version 4.1.