Rework lapacke CMake module#1083
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1083 +/- ##
=======================================
Coverage 94.90% 94.90%
=======================================
Files 64 64
Lines 2844 2844
Branches 893 893
=======================================
Hits 2699 2699
Misses 95 95
Partials 50 50 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
bfa1ef6 to
d441107
Compare
2a490b5 to
578848a
Compare
578848a to
c238c48
Compare
|
|
||
| if(NOT LAPACKE_INCLUDE_DIR) | ||
| # Derive the header location from the library path when the standard search | ||
| # above came up empty (common with non-system OpenBLAS installs). |
There was a problem hiding this comment.
Did you work out why this was the case? Does CMAKE_PREFIX_PATH always contain an include directory?
There was a problem hiding this comment.
Did you work out why this was the case?
Good question, I wonder if it is necessary. Claude added this comment but I am not sure I agree. If the _ROOT variables are not set, nor CMAKE_PREFIX_PATH, CMake should not even find the .so library.
Does CMAKE_PREFIX_PATH always contain an include directory?
I don't think so, in the case of a Spack installation of OpenBLAS it exists.
There was a problem hiding this comment.
This may search in slightly different directories. IF we can determine the difference then we could probably avoid this step
0adec5a to
6851cd6
Compare
|
Adding some tests:
It essentially improves the situation for Spack when openblas is installed out of the system paths. |
15e2d68 to
b6e0ed9
Compare
|
@EmilyBourne I did further cleaning and tests. If you look at the master branch of https://github.com/tpadioleau/tests-lapacke, we can see that the new implementation now works with openblas on macOS and out of the box with Spack (because Spack fills CMAKE_PREFIX_PATH). The tests check different configurations, from multiple OS, platforms and package managers. The failing tests on the new implementation are related to a problem of installation of atlas. What do you think ? Should we merge ? |
If everything that is failing now was also failing before then is definitely an improvement |
Fixes #936