You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed packages "openblas" and "lapack" through vcpkg, then tried to build the tensor library on top of it, using the vcpkg install dir as CMAKE_PREFIX_PATH.
This fails to find lapack. Upon deeper investigation, it turns out that Lapack is actually found, but the lapack config file introduces a new CMake target "lapack", while the tensor library expects a CMake target called LAPACK::LAPACK (CMakeLists.txt, line 116). This fails the check for the import target's existence (cmake/TensorDependencies.cmake line 54), and the CMake step aborts.
I guess there is a reason why the import target is called such, and namespacing targets is generally a good idea, but this somehow does not match the LAPACK libraries that I have here.
I can of course work around by explicitly specifying TENSOR_lapack_CXXFLAGS and TENSOR_lapack_LDFLAGS, but this is somewhat inconvenient.
The text was updated successfully, but these errors were encountered:
I have installed packages "openblas" and "lapack" through vcpkg, then tried to build the tensor library on top of it, using the vcpkg install dir as CMAKE_PREFIX_PATH.
This fails to find lapack. Upon deeper investigation, it turns out that Lapack is actually found, but the lapack config file introduces a new CMake target "lapack", while the tensor library expects a CMake target called LAPACK::LAPACK (CMakeLists.txt, line 116). This fails the check for the import target's existence (cmake/TensorDependencies.cmake line 54), and the CMake step aborts.
I guess there is a reason why the import target is called such, and namespacing targets is generally a good idea, but this somehow does not match the LAPACK libraries that I have here.
I can of course work around by explicitly specifying TENSOR_lapack_CXXFLAGS and TENSOR_lapack_LDFLAGS, but this is somewhat inconvenient.
The text was updated successfully, but these errors were encountered: