[Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON

[Ben Boeckel]

On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) wrote:
> I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file
> size is still increase 10 fold when saving pvd file to xmf format.
> 
> However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with
> -DModule_vtkIOXdmf3:BOOL=ON
> 
> cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/
> paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa -DPARAVIEW_ENABLE_PYTHON:BOOL=ON
> -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF
> -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a
> 
> I got whole bunch of boost related cmake error with cmake version 3.0.0 and
> cmake version 2.8.12.2. Some of the error messages are included at the end of
> this email.
> 
> I am able to compile RC1-22-g9ca4e44 version ok but without Module_vtkIOXdmf3
> set to ON. Is there anything on the boost side that I am not setting it right?
> I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 installed.

Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0
(which I don't believe is built using CMake anymore). It seems that it
doesn't support multiple find_package calls. Try setting
Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick
in.

--Ben