[Paraview] Install Rules for System HDF5 absent

Dave Partyka dave.partyka at kitware.com
Thu Dec 30 15:03:03 EST 2010


This isn't supported. Especially because USE_SYSTEM_ most likely means your
library is in /usr/lib on other platforms. Granted the same argument could
be made against the 4 libraries you listed. ;-)

What you could do is

1. add custom install rules via PARAVIEW_EXTRA_INSTALL_RULES_FILE ( I just
remembered you had a previous request to allow this to have multiple files.)
2. I could provide a cache variable for you to set that gets appended to
DIRS.

On Thu, Dec 30, 2010 at 1:49 PM, Michael Jackson <
mike.jackson at bluequartz.net> wrote:

> I am using a "system installed" hdf5 for my builds of ParaView. The issue
> is when I go to run the "INSTALL" rule in Visual Studio I get failures
> because the HDF5 DLL file can not be found. This is because of the following
> code::
> IF(PARAVIEW_BUILD_QT_GUI)
>  list(APPEND DIRS ${QT_BINARY_DIR} ${QT_LIBRARY_DIR})
> ENDIF(PARAVIEW_BUILD_QT_GUI)
>
> IF(VTK_USE_FFMPEG_ENCODER)
>  get_filename_component(FFMPEG_DIR "${FFMPEG_avcodec_LIBRARY}" PATH)
>  list(APPEND DIRS ${FFMPEG_DIR})
> ENDIF(VTK_USE_FFMPEG_ENCODER)
>
> IF(PARAVIEW_ENABLE_PYTHON)
>  get_filename_component(PYTHON_BIN_DIR "${PYTHON_EXECUTABLE}" PATH)
>  get_filename_component(PYTHON_LIB_DIR "${PYTHON_LIBRARY}" PATH)
>  list(APPEND DIRS ${PYTHON_BIN_DIR} ${PYTHON_LIB_DIR})
> ENDIF(PARAVIEW_ENABLE_PYTHON)
>
> IF(PARAVIEW_USE_MPI)
>  get_filename_component(MPI_LIB_DIR "${MPI_LIBRARY}" PATH)
>  get_filename_component(MPI_BIN_DIR "${MPIEXEC}" PATH)
>  list(APPEND DIRS ${MPI_LIB_DIR} ${MPI_BIN_DIR})
> ENDIF(PARAVIEW_USE_MPI)
>
> set(_extension)
> set(_dir "${PV_INSTALL_LIB_DIR}")
> IF(WIN32)
>  set(_extension ".exe")
>  set(_dir "bin")
> ENDIF(WIN32)
>
> set(APPS "\${CMAKE_INSTALL_PREFIX}/${_dir}/paraview${_extension}")  # paths
> to executables
>
> INSTALL(CODE "
>   include(\"${ParaView_CMAKE_DIR}/BundleUtilities.cmake\")
>   fixup_bundle(\"${APPS}\"   \"\"   \"${DIRS}\")
>   " COMPONENT BrandedRuntime)
>
> The issue is the "DIRS" variable which makes no attempt to add any of the
> extra directories that might be needed in case a "*_USE_SYSTEM_*" variable
> is set. I can hack in a rule for HDF5 but a much cleaner approach would be
> to track which "_USE_SYSTEM_*" variables are set and loop over those to
> setup the correct directories. Or did I just completely miss something?
>
> ___________________________________________________________
> Mike Jackson                      www.bluequartz.net
> Principal Software Engineer       mike.jackson at bluequartz.net
> BlueQuartz Software               Dayton, Ohio
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20101230/fd18ef3f/attachment.htm>


More information about the ParaView mailing list