Bug#462631: current status
Hi Francesco,
On Thu, Feb 07, 2008 at 12:23:00AM +0100, Francesco Poli wrote:
> Hi!
>
> Thanks for your ITP bug regarding Paraview!
> I hope the packaging is going on well.
You can see for yourself. Our svn is here:
XS-Vcs-Svn: svn://svn.debian.org/svn/pkg-scicomp/paraview/
XS-Vcs-Browser: http://svn.debian.org/wsvn/pkg-scicomp/paraview/
We welcome any help with the packaging.
> I wonder if you managed to link Paraview against (and make it work
> properly with) libraries already packaged and included in Debian.
Not yet. Currently we are still trying to make it compile on i386 and
amd64 together with MPI and python. We just succeeded in the compilation
itself, so at least the package builds now.
Unfortunately, the python scripting still isn't working at runtime. When
this is fixed, only then we'll try to build shared libraries and reuse
as much as possible from Debian to reduce the sice of the paraview
binary package (currently 100MB).
>
> Last time I checked, it seemed Paraview could not be linked with
> already installed libraries (without applying heavy modifications).
> I think that, from a maintainability/code-duplication point of view,
> shipping a special copy of VTK and TclTk just for Paraview would
> not be acceptable. Unfortunately though, last time I checked,
Paraview
> shipped with special versions of those libraries that had to be
> recompiled:
> http://public.kitware.com/pipermail/paraview/2006-October/003881.html
>
> I hope the situation has improved in the meanwhile: for instance,
> Paraview was going to switch from TclTk to Qt and it seems this
> transition has already been completed... Is it now possible to easily
> link Paraview against an already installed copy of VTK?
I don't know, we didn't try it yet.
> Or did you modify CMakeLists.txt in order to let Paraview compile and
> link against debianized VTK?
Not yet. First we need to make it work with all the features.
If you would like to help us, it'd be awesome. Feel free to join the
http://wiki.debian.org/Teams/DebianScientificComputingTeam
where the package is maintained.
Ondrej
Reply to: