[Pkg-scicomp-devel] paraview and python

Ondrej Certik ondrej at certik.cz
Sun Feb 17 11:15:46 UTC 2008


On Feb 16, 2008 12:25 AM, Ondrej Certik <ondrej at certik.cz> wrote:
> Hi,
>
> currently, paraview in our svn doesn't build against python (but the
> package builds just fine, even in pbuilder). To enable python, apply
> this patch:
>
> $ svn di
> Index: debian/control
> ===================================================================
> --- debian/control      (revision 2140)
> +++ debian/control      (working copy)
> @@ -3,7 +3,7 @@
>  Priority: extra
>  Maintainer: Debian Scientific Computing Team
> <pkg-scicomp-devel at lists.alioth.debian.org>
>  Uploaders: Christophe Prud'homme <prudhomm at debian.org>, Ondrej Certik
> <ondrej at certik.cz>
> -Build-Depends: cdbs (>= 0.4.51), debhelper (>= 5), autotools-dev,
> quilt (>= 0.46-4), cmake (>= 2.4.8-1), libqt4-dev (>= 4.3.3-2),
> libopenmpi-dev, python2.5, ffmpeg, libavformat-dev, libavutil-dev,
> libavcodec-dev
> +Build-Depends: cdbs (>= 0.4.51), debhelper (>= 5), autotools-dev,
> quilt (>= 0.46-4), cmake (>= 2.4.8-1), libqt4-dev (>= 4.3.3-2),
> libopenmpi-dev, python2.5, ffmpeg, libavformat-dev, libavutil-dev,
> libavcodec-dev, python2.5-dev
>  Standards-Version: 3.7.3
>  XS-DM-Upload-Allowed: yes
>  Homepage: http://www.paraview.org/
> Index: debian/rules
> ===================================================================
> --- debian/rules        (revision 2140)
> +++ debian/rules        (working copy)
> @@ -21,7 +21,7 @@
>          -DBUILD_TESTING=OFF              \
>          -DVTK_USE_FFMPEG_ENCODER=ON      \
>          -DPARAVIEW_USE_MPI=ON            \
> -        -DPARAVIEW_ENABLE_PYTHON=OFF     \
> +        -DPARAVIEW_ENABLE_PYTHON=ON      \
>          -DCMAKE_VERBOSE_MAKEFILE=ON      \
>          -DCMAKE_C_FLAGS="-O2"            \
>          -DCMAKE_CXX_FLAGS="-O2"          \
>
>
>
> However, the compilation in pbuilder then stops at:
>
> [...]
> cd /tmp/buildd/paraview-3.2.1/obj-x86_64-linux-gnu/Utilities/VTKPythonWrapping
> && /usr/bin/cc   -O2  -fPIC
> "CMakeFiles/vtkWrapPythonInit.dir/__/__/__/VTK/Wrapping/vtkWrapPythonInit.o"
>   -o ../../bin/vtkWrapPythonInit -rdynamic
> /usr/bin/cmake -E cmake_progress_report
> /tmp/buildd/paraview-3.2.1/obj-x86_64-linux-gnu/CMakeFiles
> [ 19%] Generating paraview/pv_compile_complete
> cd /tmp/buildd/paraview-3.2.1/obj-x86_64-linux-gnu/Utilities/VTKPythonWrapping/paraview
> && compile_all_pv.py
> /bin/sh: compile_all_pv.py: command not found
> make[3]: *** [Utilities/VTKPythonWrapping/paraview/pv_compile_complete]
> Error 127
> make[3]: Leaving directory `/tmp/buildd/paraview-3.2.1/obj-x86_64-linux-gnu'
> make[2]: *** [Utilities/VTKPythonWrapping/CMakeFiles/paraview_pyc.dir/all]
> Error 2
> make[2]: *** Waiting for unfinished jobs....
>
>
>
> Which I don't know how to fix. Any ideas?


So the problem was that the line

> cd /tmp/buildd/paraview-3.2.1/obj-x86_64-linux-gnu/Utilities/VTKPythonWrapping/paraview
> && compile_all_pv.py

should be

> cd /tmp/buildd/paraview-3.2.1/obj-x86_64-linux-gnu/Utilities/VTKPythonWrapping/paraview
> && python2.5 compile_all_pv.py

And this can be accomplished by this simple patch:

$ cat debian/patches/python.patch
Index: ParaView3.2.1/Utilities/VTKPythonWrapping/CMakeLists.txt
===================================================================
--- ParaView3.2.1.orig/Utilities/VTKPythonWrapping/CMakeLists.txt	2008-02-17
11:41:05.683559129 +0100
+++ ParaView3.2.1/Utilities/VTKPythonWrapping/CMakeLists.txt	2008-02-17
11:41:19.934559032 +0100
@@ -675,7 +675,7 @@
   ADD_CUSTOM_COMMAND(
     WORKING_DIRECTORY ${PV_PYTHON_MODULE_BINARY_DIR}
     COMMAND ${PYTHON_EXECUTABLE}
-    ARGS compile_all_pv.py
+    ARGS python2.5 compile_all_pv.py
     DEPENDS ${PV_PYTHON_SOURCE_FILES}
${PV_PYTHON_MODULE_BINARY_DIR}/compile_all_pv.py
     ${PV_PYTHON_OUTPUT_FILES}
     OUTPUT "${PV_PYTHON_MODULE_BINARY_DIR}/pv_compile_complete"



It is already applied in our svn repository, so all is fine now.

Ondrej



More information about the Pkg-scicomp-devel mailing list