MantisBT - ParaView
View Issue Details
0014118ParaView(No Category)public2013-06-05 16:402016-08-12 09:59
Cory Quammen 
Utkarsh Ayachit 
normalminorhave not tried
closedmoved 
 
 
TBD
incorrect functionality
0014118: VisItBridge compilation error
I have enabled PARAVIEW_USE_VISITBRIDGE using ParaView commit 3f4918784cb8aa2662d27ccdcad9b49eff2e8490 on Mac OS X. Compilation fails with

[ 94%] Building CXX object Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/vtkVisItVsReader.cxx.o
/Users/quammen/dev/build/MADAIWorkbench-Installer/bin/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.cxx: In member function ‘virtual bool vtkVisItVsReader::InitializeAVTReader(const int&)’:
/Users/quammen/dev/build/MADAIWorkbench-Installer/bin/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.cxx:102: error: cannot allocate an object of abstract type ‘avtVsFileFormat’
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/databases/Vs/avtVsFileFormat.h:41: note: because the following virtual functions are pure within ‘avtVsFileFormat’:
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtFileFormat.h:150: note: virtual const char* avtFileFormat::GetType()
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:129: note: virtual vtkDataSet* avtSTMDFileFormat::GetMesh(int, const char*)
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:130: note: virtual vtkDataArray* avtSTMDFileFormat::GetVar(int, const char*)
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:140: note: virtual void avtSTMDFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)
make[3]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/vtkVisItVsReader.cxx.o] Error 1
make[2]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error 2
make[1]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/rule] Error 2
make: *** [vtkIOVisItBridge] Error 2
No tags attached.
txt CMakeCache.txt (354,387) 2013-06-11 15:08
https://www.vtk.org/Bug/file/9463/CMakeCache.txt
Issue History
2013-06-05 16:40Cory QuammenNew Issue
2013-06-07 12:03Utkarsh AyachitNote Added: 0030977
2013-06-07 12:03Utkarsh AyachitAssigned To => Utkarsh Ayachit
2013-06-11 15:08Cory QuammenFile Added: CMakeCache.txt
2013-06-11 15:08Cory QuammenNote Added: 0030982
2013-06-11 16:03Cory QuammenNote Added: 0030985
2013-06-11 17:44Cory QuammenNote Added: 0030987
2016-08-12 09:59Kitware RobotNote Added: 0038404
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved

Notes
(0030977)
Utkarsh Ayachit   
2013-06-07 12:03   
Can you attach your CMakeCache.txt? Are you using system HDF5?
(0030982)
Cory Quammen   
2013-06-11 15:08   
CMakeCache.txt attached. I am not using system HDF5.
(0030985)
Cory Quammen   
2013-06-11 16:03   
I do have an HDF5 installation in /opt/local. Boost is also installed there, so Boost_INCLUDE_DIR is set to /opt/local/include. This is added to the VISITBRIDGE_INCLUDE_DIRS, so there is a danger that the wrong HDF5 header files are being located.
(0030987)
Cory Quammen   
2013-06-11 17:44   
I just confirmed it's a problem with my installation of HDF5 using mac ports. The installed version was 1.6.9. The header for this version was getting included, so the majority of the content for avtVsFileFormat.h and avtVsFileFormat.C was skipped by the preprocessor because of the check

#if HDF5_VERSION_GE(1, 8, 1)

at avtVsFileFormat.h:64

A solution migt be to include the VTK HDF5 include directories before any system include directories.
(0038404)
Kitware Robot   
2016-08-12 09:59   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.