Re: [Paraview] VTK version
It is 5.6.0 + some additional patches as VTK 5.6.0 was released before ParaView 3.8.0 was finished. If you checkout the VTK release branch. The commit ParaView 3.8.0 used was: 8b2449871dca83d542cc7d8093da5fee3c70ebb1 Author: Dave DeMarle dave.dema...@kitware.com 2010-05-19 14:25:56 Committer: David Partyka dave.part...@kitware.com 2010-05-21 08:59:24 Parent: 33a0bc981c98fc81bc5351ad27ad018e9cdc6dc1 (STYLE: Remove tabs.) Child: 9fcf02d503c6fb13fa5104deb3956a77ff079a3a (COMP: SetNumberOfHistogramBins(int*) missing definition, added) Branches: release, remotes/origin/release Follows: v5.6.0 Precedes: Take timestamps of key portions of parallel rendering algorithm. Is there an easy to get the diff between the released vtk-5.6.0 and and the branch used in paraview-3.8.0? Francois ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] xdmf.py install is scanning my /usr recursively and try to bytecompile anything in .py
Hi Francois,
I am a little bit confused by your email. Just to be clear, is this the
change you are proposing?
SET( XdmfGzipSource
gzstream
@@ -504,7 +504,7 @@ IF(XDMF_WRAP_PYTHON)
# Compile Byte Code
INSTALL(CODE EXECUTE_PROCESS(COMMAND ${PYTHON_EXECUTABLE}
${Xdmf_SOURCE_DIR}/CMake/CompileXdmfByteCode.py
-${CMAKE_INSTALL_PREFIX}/${XDMF_WRAP_PYTHON_INSTALL_PY_DIR}))
+${XDMF_WRAP_PYTHON_INSTALL_DIR}))
ENDIF(XDMF_WRAP_PYTHON)
Let me know and I will gladly commit the fix.
Hi Dave,
Sorry for the delay. I now believe there may be a better fix respecting
DESTDIR as the python modules of vtk don't exhibit this problem.
I have to look it up a little bit further.
Francois
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] The DISTDIR variable is expanded twice when installing PointSpriteDemo
Thanks for reporting this. It has been fixed on master and will be
included in 3.8.1 release.
http://paraview.org/Bug/view.php?id=10815
What about the double expansion of DESTDIR? The bug only mention respecting
BUILD_EXAMPLES.
I am not sure it is where it was meant to go but I applied this patch to make
it respect DESTDIR and finally land in /usr/bin under linux.
I didn't do a complete analysis of what goes wrong with ${PROJECT_BINARY_DIR}
and just replaced it by ${PV_INSTALL_BIN_DIR}.
Francois
--- Plugins/PointSprite/Examples/Rendering/Cxx/CMakeLists.txt.orig 2010-06-11 22:54:37.423952532 +1200
+++ Plugins/PointSprite/Examples/Rendering/Cxx/CMakeLists.txt 2010-06-11 22:55:07.546951156 +1200
@@ -6,5 +6,5 @@
target_link_libraries(${exe} PointSprite_Rendering vtkIO)
install(TARGETS ${exe}
-RUNTIME DESTINATION ${PROJECT_BINARY_DIR}
+RUNTIME DESTINATION ${PV_INSTALL_BIN_DIR}
)
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
[Paraview] xdmf.py install is scanning my /usr recursively and try to bytecompile anything in .py
Hi,
A problem that I encountered while packaging paraview-3.8.0.
Here is a build log extract:
-- Installing: /media/anthill/portage/sci-
visualization/paraview-3.8.0/image/usr/lib/python2.6/site-
packages/Xdmf/__init__.py
-- Installing: /media/anthill/portage/sci-
visualization/paraview-3.8.0/image/usr/lib/python2.6/site-
packages/Xdmf/Xdmf.py
Listing /usr/ ...
Listing /usr/bin ...
Compiling /usr/bin/add_esri_column.py ...
Sorry [Errno 13] Permission denied: '/usr/bin/add_esri_column.pyc'
Compiling /usr/bin/build_pcs.py ...
Sorry [Errno 13] Permission denied: '/usr/bin/build_pcs.pyc'
snip
Listing /usr/i686-pc-linux-gnu ...
Listing /usr/i686-pc-linux-gnu/bin ...
Listing /usr/i686-pc-linux-gnu/binutils-bin ...
Listing /usr/i686-pc-linux-gnu/binutils-bin/2.20.1 ...
Listing /usr/i686-pc-linux-gnu/gcc-bin ...
Listing /usr/i686-pc-linux-gnu/gcc-bin/3.3 ...
Listing /usr/i686-pc-linux-gnu/gcc-bin/4.3.4 ...
Listing /usr/i686-pc-linux-gnu/gcc-bin/4.4.3 ...
Listing /usr/i686-pc-linux-gnu/lib ...
snip
Listing /usr/src/linux-2.6.32-gentoo-r7/virt/kvm ...
Listing /usr/tmp-vrooom ...
-- Installing: /media/anthill/portage/sci-
visualization/paraview-3.8.0/image/usr/lib/paraview-3.8/libXdmf.so
So two points: first it doesn't respect DESTDIR - in the end bytecompiling is
the responsibility of the package manager so I disabled that completely.
Second it all come from this bit in Utilities/Xdmf2/libsrc/CMakeList.txt
(lines 505-507):
# Compile Byte Code
INSTALL(CODE EXECUTE_PROCESS(COMMAND ${PYTHON_EXECUTABLE}
${Xdmf_SOURCE_DIR}/CMake/CompileXdmfByteCode.py
${CMAKE_INSTALL_PREFIX}/${XDMF_WRAP_PYTHON_INSTALL_PY_DIR}))
It turns out that we scan /usr which is CMAKE_INSTALL_PREFIX because
XDMF_WRAP_PYTHON_INSTALL_PY_DIR is never defined. I suspect the intent
was to define it earlier and to use it to set XDMF_WRAP_PYTHON_INSTALL_DIR
as we can see earlier in the same file (lines 472):
SET(XDMF_WRAP_PYTHON_INSTALL_DIR
${CMAKE_INSTALL_PREFIX}${XDMF_WRAP_PYTHON_INSTALL_DIR}/Xdmf)
Which I think may have been meant:
SET(XDMF_WRAP_PYTHON_INSTALL_DIR
${CMAKE_INSTALL_PREFIX}${XDMF_WRAP_PYTHON_INSTALL_PY_DIR}/Xdmf)
--
If we don't care about DESTDIR replacing
${CMAKE_INSTALL_PREFIX}/${XDMF_WRAP_PYTHON_INSTALL_PY_DIR}
in line 507 by:
${XDMF_WRAP_PYTHON_INSTALL_DIR}
will look in the right place.
Francois
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] The DISTDIR variable is expanded twice when installing PointSpriteDemo
Thanks for reporting this. It has been fixed on master and will be included in 3.8.1 release. http://paraview.org/Bug/view.php?id=10815 What about the double expansion of DESTDIR? The bug only mention respecting BUILD_EXAMPLES. Francois ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Why does paraview want to install its own duplicate of QT libraries?
Hi, I am trying to update the ebuild for the gentoo linux distribution. My current process died at install time: -- Installing: /media/anthill/portage/sci- visualization/paraview-3.8.0/image/usr/bin/paraview -- Installing: /media/anthill/portage/sci- visualization/paraview-3.8.0/image/usr/lib/paraview-3.8/paraview-real -- Installing /usr/lib/paraview-3.8/libQtCore.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtGui.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtNetwork.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtXml.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtSql.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtHelp.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtWebKit.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtCLucene.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtXmlPatterns.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtDBus.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.8/libQtOpenGL.so tar: /usr/lib/paraview-3.8: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing: /media/anthill/portage/sci- visualization/paraview-3.8.0/image/usr/lib/paraview-3.8/sqldrivers -- Installing: /media/anthill/portage/sci- visualization/paraview-3.8.0/image/usr/lib/paraview-3.8/sqldrivers/libqsqlmysql.so -- Installing: /media/anthill/portage/sci- visualization/paraview-3.8.0/image/usr/lib/paraview-3.8/sqldrivers/libqsqlite.so -- Installing: /media/anthill/portage/sci- visualization/paraview-3.8.0/image/usr/lib/paraview-3.8/.plugins --- There are several issues in this simple log: -First the install procedure for the QT libraries doesn't seem to respect the DESTDIR variables. -Second why the heck do you want to have a copy of the QT libraries provided by the system inside the paraview library folder? It was not needed by paraview 3.6.x and if it is needed now, it means something is seriously broken. Francois ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView 3.6.2 Release and hdf5-1.8
On Fri, 08 Jan 2010 10:21:22 Favre Jean wrote:
I have tried compiling pv3.6.2 with my system's hdf5 and have run into the
following issue:
regardless of what api-version I use to configure compile hdf5 (v16 or
v18), I cannot compile pv because of the following error:
/apps-vis/ParaView3-6-2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:174: error:
braces around scalar initializer for type ‘herr_t (*)(H5FD_t*, unsigned
char*, unsigned int, hbool_t)’ Badly placed (.
/apps-vis/ParaView3-6-2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:174: error:
invalid conversion from ‘haddr_t (*)(H5FD_t*)’ to ‘herr_t (*)(H5FD_t*,
H5FD_mem_t, hid_t, haddr_t, hsize_t)’ Badly placed (.
etc.
here is my last config for hdf5:
./configure --enable-parallel --enable-linux-lfs --enable-shared
--with-default-api-version=v18
The good news:
I was able to make the compilation finish after copying XdmfH5Driver.cxx
from the CVS version of ParaView. And so far in execution trials, nothing
has broken.
Has anyone else seen this? I had initially configured hdf5 with the default
(i.e without specifying the last option --with-default-api-version=v??).
I then tried with v16, and v18, and in both cases, I could not compile,
until I overwrote the source with the cvs copy.
In Gentoo we have a patch for XdmfH5Driver.cxx - It was introduced for
paraview 3.6.1 but it may still be current.
I am attaching for reference. One thing to note conditional compilation is
introduced for HDF5 v1.6 and 1.8. From the look of the patch the code
that is left alone is geared to HDF5 v1.8 but paraview ship with version 1.6
so paraview version may have been patched to include some v1.8 bits.
Most interesting are these 2 bits that are not conditional:
@@ -159,6 +165,7 @@
H5FD_dsm_close, /*close */
H5FD_dsm_cmp, /*cmp */
NULL, /*query */
+NULL, /*type map */
NULL, /*alloc */
NULL, /*free */
H5FD_dsm_get_eoa, /*get_eoa */
@@ -168,6 +175,7 @@
H5FD_dsm_read, /*read */
H5FD_dsm_write, /*write */
NULL, /*flush */
+NULL, /*truncate */
NULL, /*lock */
NULL, /*unlock*/
H5FD_FLMAP_SINGLE /*fl_map*/
this is in the definition of H5FD_class_t H5FD_dsm_g, that would fit with your
error message ie line 174 the definition supplied is too short and misses some
fields.
diff -Naur ParaView3/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx ParaView3.new/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx
--- ParaView3/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx 2009-07-20 15:39:10.0 -0400
+++ ParaView3.new/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx 2009-07-22 16:05:22.0 -0400
@@ -132,9 +132,15 @@
static herr_t H5FD_dsm_flush(H5FD_t *_file);
#endif
static int H5FD_dsm_cmp(const H5FD_t *_f1, const H5FD_t *_f2);
+#ifdef H5_USE_16_API
+static haddr_t H5FD_dsm_get_eoa(const H5FD_t *_file, H5FD_mem_t);
+static herr_t H5FD_dsm_set_eoa(H5FD_t *_file, H5FD_mem_t, haddr_t addr);
+static haddr_t H5FD_dsm_get_eof(const H5FD_t *_file);
+#else
static haddr_t H5FD_dsm_get_eoa(H5FD_t *_file);
static herr_t H5FD_dsm_set_eoa(H5FD_t *_file, haddr_t addr);
static haddr_t H5FD_dsm_get_eof(H5FD_t *_file);
+#endif
static herr_t H5FD_dsm_read(H5FD_t *_file, H5FD_mem_t type, hid_t fapl_id, haddr_t addr,
DSM_HSIZE_T size, void *buf);
static herr_t H5FD_dsm_write(H5FD_t *_file, H5FD_mem_t type, hid_t fapl_id, haddr_t addr,
@@ -159,6 +165,7 @@
H5FD_dsm_close, /*close */
H5FD_dsm_cmp, /*cmp */
NULL, /*query */
+NULL, /*type map */
NULL, /*alloc */
NULL, /*free */
H5FD_dsm_get_eoa, /*get_eoa */
@@ -168,6 +175,7 @@
H5FD_dsm_read, /*read */
H5FD_dsm_write, /*write */
NULL, /*flush */
+NULL, /*truncate */
NULL, /*lock */
NULL, /*unlock*/
H5FD_FLMAP_SINGLE /*fl_map*/
@@ -594,7 +602,11 @@
*-
*/
static haddr_t
+#ifdef H5_USE_16_API
+H5FD_dsm_get_eoa(const H5FD_t *_file, H5FD_mem_t)
+#else
H5FD_dsm_get_eoa(H5FD_t *_file)
+#endif
{
H5FD_dsm_t *file = (H5FD_dsm_t*)_file;
@@ -622,7 +634,11 @@
*-
*/
static herr_t
+#ifdef H5_USE_16_API
+H5FD_dsm_set_eoa(H5FD_t *_file, H5FD_mem_t,
Re: [Paraview] rotating and shifting image data
On Thu, 26 Nov 2009 07:57:16 Martin Luessi wrote: However, the vtkImageReslice filter does not seem to be present in the VTK version that comes with ParaView (3.6.1-r1 on Gentoo). (Apart from this I couldn't figure out how to use VTK filters on simple.ImageReader) vtkImageReslice seems to be in the source tarball on my Gentoo system. There is a few issues on Gentoo may be you should file a bug. Actually speaking of bugs can you take a screenshot? I cannot I get failed to create pixmap and then a segfault. I cannot quite figure what's wrong apart may be a bug in my openGL drivers. Francois ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
