[MOAB-dev] building vtkMoabReader

Thu Feb 19 14:03:48 CST 2015

Jacob,

I downloaded and installed paraview 4.3.1 from source and am not able
to replicate your errors. I do see all the necessary cmake files
installed under lib/cmake/paraview-4.3. Please configure paraview with
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON option and re-install.
Locally, I have:

vijaysm at tachyon > find
/usr/software/paraview/4.3.1/lib/cmake/paraview-4.3/*.cmake | wc -l
66

And not 0 as shown in your installation. Also, your "Note" seems to be
generated from a build directory. Did you specify an install prefix
during paraview configure and run make install ?

It does however fail for various other reasons. My errors below:

---------------
CMake Warning at
/usr/software/paraview/4.3.1/lib/cmake/paraview-4.3/ParaViewPlugins.cmake:981
(message):
  GUI resource files in plugins are no longer supported.  The same
  functionality can be obtained using Hints in the Server Manager xml files.
  See the Major API Changes document for details.
Call Stack (most recent call first):
  CMakeLists.txt:35 (add_paraview_plugin)

CMake Warning (dev) at CMakeLists.txt:41 (target_link_libraries):
  Policy CMP0023 is not set: Plain and keyword target_link_libraries
  signatures cannot be mixed.  Run "cmake --help-policy CMP0023" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  The keyword signature for target_link_libraries has already been used with
  the target "vtkMoabReaderPlugin".  All uses of target_link_libraries with a
  target should be either all-keyword or all-plain.
---------------

This looks like an issue with the way we are trying to add our custom
plugin to paraview and should be fixable in a backward compatible way.
I'll keep you updated when we push a fix for this. Thanks for
reporting the incompatibility.

Vijay

On Wed, Feb 18, 2015 at 1:40 PM, Hochhalter, Jacob Dean (LARC-D309)
<jacob.d.hochhalter at nasa.gov> wrote:
> Vijay,
>
> Thanks for your response.  I have those settings for the moab definitions.  However, for paraview v4.3.1, the paraview cmake file is put in the top level of the build directory (see note 1, below), and only the separate module cmake files are in the path that you suggested (see note 2, below).  Nonetheless, I am pointing the paraview_dir to the directory containing the paraview cmake file.
>
> I previously tried paraview 4.0.1, but still saw that error from cmake regarding the extra "Plugin_Plugin" in the c++ file name.  I was thinking that was an issue with the cmake files with moab, or something that I was doing wrong, but likely not having to do with paraview.  Do your vtkMoabReader file names have that additional "Plugin_Plugin" appended?
>
> Thanks,
> - Jake
>
>
> Note #1:
> tara paraview_build # ls *.cmake
> cmake_install.cmake               ParaViewConfig.cmake
> CTestCustom.cmake                 ParaViewConfigVersion.cmake
> CTestTestfile.cmake               ParaViewData_config.cmake
> ParaViewCompileToolsConfig.cmake  ParaViewTargets.cmake
>
> Note #2:
> tara paraview_build # ls lib/cmake/paraview-4.3/
> Modules
> tara paraview_build # ls lib/cmake/paraview-4.3/Modules/P*cmake
> lib/cmake/paraview-4.3/Modules/Pygments.cmake
> lib/cmake/paraview-4.3/Modules/Pygments-Headers.cmake
>
>
> ________________________________________
> From: Vijay S. Mahadevan [vijay.m at gmail.com]
> Sent: Wednesday, February 18, 2015 2:05 PM
> To: Hochhalter, Jacob Dean (LARC-D309)
> Cc: moab-dev at mcs.anl.gov
> Subject: Re: [MOAB-dev] building vtkMoabReader
>
> Jacob,
>
> My vtkMoabReader works fine (v4.8.0) with Paraview v4.0.1. But I
> assume v4.3.1 might have some changes that could cause a breakage
> here.
>
> Can you make sure that:
> MOAB_INCLUDE_DIRS := PATH_TO_MOAB_INSTALLATION/include
> MOAB_LIBRARY := PATH_TO_MOAB_INSTALLATION/lib/libMOAB.so
> ParaView_DIR := PATH_TO_PARAVIEW_INSTALLATION/lib/cmake/paraview-*
>
> The ParaView_DIR needs to point to the CMake file location and not at
> the installation directory. If these are already your settings, let us
> know and we'll check with Paraview v4.3.1. We haven't tested with the
> latest Paraview versions in some time and if things have changed, we
> can certainly push a fix.
>
> Vijay
>
> On Wed, Feb 18, 2015 at 12:40 PM, Hochhalter, Jacob Dean (LARC-D309)
> <jacob.d.hochhalter at nasa.gov> wrote:
>> Hello,
>>
>> I am trying to build the vtkMoabReader, and am running into an issue that I am hoping someone can shed some light on.  I have not been able to find any build instructions for this tool in the version of moab that I downloaded, 4.8.0, so I could be missing something simple.  I did find some for an older version, and tried to mimic those.
>>
>> Here is an outline of my steps:
>>
>> 1)  Download/build Paraview v4.3.1 from source in paraview_build_dir with python and hdf5 enabled, but everything else left as defaults
>> 2)  Download moab-4.8.0 and configure using './configure --prefix=/opt/moab/moab-4.8.0/ --enable-shared --enable-vtkMOABReader --with-vtk=paraview_build_dir --with-vtk-lib-suffix=-pv4.3'  This build appears to go fine, and I end up with executables and libs in the install dir.  However, there is nothing for the vtkMoabReader installed.
>> 3)  cd to tools/vtkMOABReader and run ccmake, which (after defining moab and paraview dirs) returns an error that
>>
>>     "
>>      CMake Error at
>>      ParaView-v4.3.1-source/CMake/ParaViewPlugins.cmake:1080
>>      (ADD_LIBRARY):
>>        Cannot find source file:
>>
>>          ./vtkMoabReader.cxx
>>
>>        Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx
>>      Call Stack (most recent call first):
>>        CMakeLists.txt:35 (add_paraview_plugin)
>>
>>     "
>>
>>     Note:  There is a file under vtkMOABReader called vtkMoabReaderPlugin_Plugin.cxx, but not vtkMoabReader.cxx.  Also, the same thing occurred when I tried moab v4.7.
>> 4) out of curiosity, I renamed the generated vtkMoabReaderPlugin_Plugin.cxx to  vtkMoabReader.cxx, which gets me past that error, but then ccmake returns another error:  missing paraview include file, CellSets.h.  However, there is no include file named CellSets.h inside this version of paraview; the closest is Cell.h.
>>
>> Any pointers regarding things I might be missing, or known working configurations would be much appreciated.
>>
>> Thanks!
>> - Jake