[CMake] [ANNOUNCE] CMake 3.15.0-rc4 is ready for testing

2019-07-10 Thread Robert Maynard
I am proud to announce the fourth CMake 3.15 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.15 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.15/release/3.15.html Some of the more significa

Re: [CMake] FindBLAS + MKL + Ctest fails on MacOS (SIP)

2019-07-10 Thread Luke D'Alessandro
> On Jul 10, 2019, at 4:42 AM, Eric Doenges wrote: > > The simplest way to do this is to use the BUILD_RPATH and/or INSTALL_RPATH > properties, i.e. something like: > > list(GET BLAS_LIBRARIES 0 _BLAS_FIRSTLIB) > get_filename_component(_BLAS_LIBDIR "${_BLAS_FIRSTLIB}" DIRECTORY > set_target_p

Re: [CMake] getting compiler's include paths

2019-07-10 Thread Robert Maynard
I am not an user of ctags. But CMake supports generating a `compile_commands.json` for the Makefile and Ninja generator ( https://cmake.org/cmake/help/latest/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html ). That will have all the include directories for each target. On Sun, Jul 7, 2019 at 10:27 AM j

Re: [CMake] FindBLAS + MKL + Ctest fails on MacOS (SIP)

2019-07-10 Thread Eric Doenges
The simplest way to do this is to use the BUILD_RPATH and/or INSTALL_RPATH properties, i.e. something like: list(GET BLAS_LIBRARIES 0 _BLAS_FIRSTLIB) get_filename_component(_BLAS_LIBDIR "${_BLAS_FIRSTLIB}" DIRECTORY set_target_properties(test_blas PROPERTIES BUILD_RPATH "${_BLAS_LIBDIR}") This