[Paraview] Paraview server using off-screen rendering

[Chuck Atkins]

>
> If it's a problem with HDF5 library, I'm not sure where I need to point to
>>> the system installation.
>>>
>> If you load the cray-hdf5 module, that will set the HDF5_DIR environment
>> variable to the correct location.  Unfortunately, CMake uses the HDF5_ROOT
>> variable instead to look for it so you'll neet to set it accordingly.
>>
> I don't have much experience with cmake, but can I set additional
> variables in the ccmake window? Should this variable show up there asking
> to be set if you turn on the advanced mode toggle?
>

Different find modules work differently.  The FindHDF5 module uses the
HDF5_ROOT environment variable (not CMake variable, which is why it won't
show up in the ccmake UI) as a hint for where to search, hence exporting it
as an env var prior to running CMake.  You'll also want to be sure to
specify to use an external HDF5 rather than ParaView building it's own:

  -DVTK_USE_SYSTEM_HDF5:BOOL=ON


 CMAKE_CXX_FLAGS                  -L/lustre/medusa/gantech/
> software/mesa-10.6.0/lib
>
...

>  CMAKE_C_FLAGS                    -L/lustre/medusa/gantech/
> software/mesa-10.6.0/lib
>
...

>  CMAKE_EXE_LINKER_FLAGS           -L/lustre/medusa/gantech/
> software/mesa-10.6.0/lib
>

Instead of setting these in the compiler flags, it's better to tell
ParaView where to explicitly find the libraries and to configure
accordingly for OSMesa.  You can pass these as command line arguments to
cmake or ccmake with -D, or set them in the ccmake UI:

  -DOPENGL_INCLUDE_DIR:PATH=
  -DOPENGL_xmesa_INCLUDE_DIR:PATH=
  -DOPENGL_gl_LIBRARY:FILEPATH=
  -DOPENGL_glu_LIBRARY:FILEPATH=
  -DOSMESA_INCLUDE_DIR:PATH=/lustre/medusa/gantech/
software/mesa-10.6.0/include
  -DOSMESA_LIBRARY:FILEPATH=/lustre/medusa/gantech/
software/mesa-10.6.0/lib/libOSMesa.a
  -DVTK_OPENGL_HAS_OSMESA:BOOL=ON
  -DVTK_USE_X:BOOL=OFF



>  CMAKE_Fortran_COMPILER           /opt/gcc/4.9.2/bin/gfortran
>

Not that it will really matter since we're not compiling Fortran code, but
this should be /opt/cray/craype/2.2.1/bin/ftn


 MPI_CXX_LIBRARIES                /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/
>
...

>  MPI_C_LIBRARIES                  /opt/cray/mpt/7.1.3/gni/
> mpich2-gnu/49/lib/
>
...

>  MPI_LIBRARY                      /opt/cray/mpt/7.1.3/gni/
> mpich2-gnu/49/lib
>

It does look like the wrappers are correctly getting used for mpicc and
mpiCC and you can see the include dirs getting set accordingly, but these
do not look right.  Which version of CMake are you using?  Here's what I
get using CMake 3.2.3 (current cmake) on a Cray XC30 when not setting any
MPI variables, just letting CMake auto-detect them by enabling
ParaView_USE_MPI=ON:

 MPI_CXX_COMPILER
/opt/cray/craype/2.1.0/bin/CC
 MPI_CXX_COMPILE_FLAGS

 MPI_CXX_INCLUDE_PATH

 MPI_CXX_LIBRARIES

 MPI_CXX_LINK_FLAGS

 MPI_CXX_NO_INTERROGATE
/opt/cray/craype/2.1.0/bin/CC
 MPI_C_COMPILER
/opt/cray/craype/2.1.0/bin/cc
 MPI_C_COMPILE_FLAGS

 MPI_C_INCLUDE_PATH

 MPI_C_LIBRARIES

 MPI_C_LINK_FLAGS

 MPI_C_NO_INTERROGATE
/opt/cray/craype/2.1.0/bin/cc
 MPI_EXTRA_LIBRARY
MPI_EXTRA_LIBRARY-NOTFOUND
 MPI_Fortran_COMPILER
/opt/cray/craype/2.1.0/bin/ftn
 MPI_Fortran_COMPILE_FLAGS

 MPI_Fortran_INCLUDE_PATH

 MPI_Fortran_LIBRARIES

 MPI_Fortran_LINK_FLAGS

 MPI_Fortran_NO_INTERROGATE
/opt/cray/craype/2.1.0/bin/ftn
 MPI_LIBRARY                      MPI_LIBRARY-NOTFOUND

Because the Cray wrappers automatically add the mpi libs and headers
(behaving like mpiCC), then the MPI code should compile without any
additional flags.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/dba8e34f/attachment.html>