Mike Jackson wrote:
Can you post your module or attach it to a bug/feature request? I also have a FindHDF5 module and I would like to compare the two.
Sorry about that, I meant to attach the module to the first email. It is attached to this one.
--Will
Mike Jackson www.bluequartz.net On Tue, Jul 7, 2009 at 11:03 AM, Will Dicharry<wdicha...@stellarscience.com> wrote:Hi All, I have written a find module that invokes the hdf5 wrapper compiler to determine libraries and includes that are necessary for clients of HDF5. I tried to follow the guidelines for formatting and naming set forth in the module readme. At the moment, the module has been tested on Linux, AIX, and Cray (CNL) systems. I would be happy to be the maintainer for this module if there is desire to place it in the CMake distribution. Thanks, Will -- Will Dicharry Software Developer Stellar Science Ltd Co _______________________________________________ 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 CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
-- Will Dicharry Software Developer Stellar Science Ltd Co
# - Find the HDF5 library. # # This module invokes the HDF5 wrapper compiler that should be installed # alongside HDF5. Depending upon the HDF5 Configuration, the wrapper compiler # is called either h5cc or h5pcc. If this succeeds, the module will then call # the compiler with the -show argument to see what flags are used when compiling # an HDF5 client application. # # This module will define the following variables: # HDF5_INCLUDE_DIRS - location of the hdf5 includes # HDF5_LIBRARIES - link libraries for HDF5 # HDF5_FOUND - true if HDF5 was found on the system # HDF5_LIBRARY_DIRS - the full set of library directories # HDF5_COMPILER_EXECUTABLE - the path to the HDF5 wrapper compiler include(FindPackageHandleStandardArgs) # try to find the HDF5 wrapper compiler find_program( HDF5_COMPILER_EXECUTABLE NAMES h5cc h5pcc DOC "HDF5 Wrapper compiler. Used only to detect HDF5 compile flags." ) mark_as_advanced( HDF5_COMPILER_EXECUTABLE ) if( HDF5_INCLUDE_DIRS AND HDF5_LIBRARIES ) # Do nothing: we already have HDF5_INCLUDE_PATH and HDF5_LIBRARIES in the # cache, it would be a shame to override them elseif( HDF5_COMPILER_EXECUTABLE ) exec_program( ${HDF5_COMPILER_EXECUTABLE} ARGS -show OUTPUT_VARIABLE HDF5_COMPILE_CMDLINE RETURN_VALUE HDF5_COMPILER_RETURN ) if( HDF5_COMPILER_RETURN EQUAL 0 ) # do nothing else() message( STATUS "Unable to determine HDF5 from HDF5 wrapper." ) endif() endif() if( HDF5_INCLUDE_PATH AND HDF5_LIBRARIES ) # do nothing elseif( HDF5_COMPILE_CMDLINE ) # grab the hdf5 libraries from the command line. We will use the path of # these things to find the include dirs # First: linker paths string( REGEX MATCHALL "-L([^\" ]+|\"[^\"]+\")" HDF5_ALL_LINK_PATHS "${HDF5_COMPILE_CMDLINE}" ) set( HDF5_LINK_PATH ) set( HDF5_ALL_INCLUDE_PATHS ) foreach( LPATH ${HDF5_ALL_LINK_PATHS} ) string( REGEX REPLACE "^-L" "" LPATH ${LPATH} ) string( REGEX REPLACE "//" "/" LPATH ${LPATH} ) list( APPEND HDF5_LINK_PATH ${LPATH} ) # The HDF wrapper compiler assumes that hdf5.h will be somewhere in your # sytem include path and doesn't appear to specify the location of the # includes. We make a guess here that the includes may be somewhere in # the standard *nix layout relative to the lib directory. set( IPATH ${LPATH}/../include ) list( APPEND HDF5_ALL_INCLUDE_PATHS ${IPATH} ) endforeach() # now search for the library names required by HDF (match -l...) # match only -l's preceded by a space or comma # this is to exclude directory names like xxx-linux/ string( REGEX MATCHALL "[, ]-l([^\", ]+)" HDF5_ALL_LIBRARY_FLAGS "${HDF5_COMPILE_CMDLINE}" ) # strip the -l from all of the library flags and add to the search list # we seed the list of library names with the plain hdf5 C libraries. # However, we need to search for other libraries because HDF5 relies on a # couple of things depending upon how it was compiled. An example of this # problem is when HDF is compiled with SZip support. set( HDF5_LIBRARY_NAMES hdf5 hdf5_hl ) foreach( LIB ${HDF5_ALL_LIBRARY_FLAGS} ) string( REGEX REPLACE "^[, ]-l" "" LIB ${LIB} ) list( APPEND HDF5_LIBRARY_NAMES ${LIB} ) endforeach() set( HDF5_LIBRARIES ) foreach( LIB ${HDF5_LIBRARY_NAMES} ) find_library( HDF5_${LIB}_LIBRARY ${LIB} HINTS ${HDF5_LINK_PATH} ) list( APPEND HDF5_LIBRARIES ${HDF5_${LIB}_LIBRARY} ) mark_as_advanced( HDF5_${LIB}_LIBRARY ) endforeach() # look for the include paths find_path( HDF5_INCLUDE_DIRS hdf5.h /usr/local/include /usr/include $ENV{HOME}/.local/include ${HDF5_ALL_INCLUDE_PATHS} ) endif() mark_as_advanced( HDF5_INCLUDE_DIRS ) mark_as_advanced( HDF5_LIBRARIES ) find_package_handle_standard_args( HDF5 DEFAULT_MSG HDF5_LIBRARIES HDF5_INCLUDE_DIRS )
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ 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 CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake