Trying to build HDF5 1.8.6 with CMake, getting undefined externals?

Actually, the FIND_PACKAGE command does exactly that: It looks for a file
called FindHDF5.cmake, first in <cmake-install>/share/cmake-2.8/Modules
and then in any directory mentioned by CMAKE_MODULE_PATH.

It's the Find<package-name>.cmake's job to look for and include a
configuration file that defines usefile things like <package-name>_DIR
<package-name>_LIBS and <package_name>_INCLUDE_DIRS

The FindHDF5.cmake included in CMake 2.8.4 is outdated and bogus.

Just a precision, when I said "we no longer use the FindHDF5.cmake
    file which comes with cmake", I actually meant, we do not use any
    FindHDF5.cmake file at all (thanks to John). The FIND_PACKAGE(HDF5
    "1.8.6" REQUIRED NO_MODULE) command is sufficient, it will ask for
    the HDF5_DIR to be set (if it is not found automatically).
    Everything is then picked up from the hdf5 target and config files
    (even the MPI libraries used during the compilation of hdf5 if the
    parallel mode has been enabled).

···

From: Jerome Soumagne <soumagne@cscs.ch>

________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
________________________________

that's why we use the NO_MODULE option of the FIND_PACKAGE command. The FindHDF5.cmake file is only useful when hdf5 is built without cmake, ie. with configure. When hdf5 is built with cmake, it then installs cmake configuration files with lib targets, config, etc, everything is then much simpler in the sense that everything is picked up automatically.

···

On 03/16/2011 03:48 PM, Williams, Norman K wrote:

Actually, the FIND_PACKAGE command does exactly that: It looks for a file
called FindHDF5.cmake, first in<cmake-install>/share/cmake-2.8/Modules
and then in any directory mentioned by CMAKE_MODULE_PATH.

It's the Find<package-name>.cmake's job to look for and include a
configuration file that defines usefile things like<package-name>_DIR
<package-name>_LIBS and<package_name>_INCLUDE_DIRS

The FindHDF5.cmake included in CMake 2.8.4 is outdated and bogus.

From: Jerome Soumagne<soumagne@cscs.ch>
Just a precision, when I said "we no longer use the FindHDF5.cmake
     file which comes with cmake", I actually meant, we do not use any
     FindHDF5.cmake file at all (thanks to John). The FIND_PACKAGE(HDF5
     "1.8.6" REQUIRED NO_MODULE) command is sufficient, it will ask for
     the HDF5_DIR to be set (if it is not found automatically).
     Everything is then picked up from the hdf5 target and config files
     (even the MPI libraries used during the compilation of hdf5 if the
     parallel mode has been enabled).

________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
________________________________

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org