> 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
>
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
Hi all,
I have one of those complex interactions that results in an issue where it’s
not clear to me which component is responsible.
I have unit tests written using CTest that depend on Intel's MKL BLAS
implementation. I use find_package(BLAS) and link the test executables to
