Yes, that seems to be a new feature. I was thinking about it. There are a few considerations:
1) Recently updated sextractor and scamp can use openblas instead but psfex still can't (maybe an update for psfex is on the way as well?). So, for now we should be consistent probably. For example, users who compile sextractor against openblas then need to remove openblas and install atlas-lapack to compile psfex.
2) I can change dependencies from atlas-lapack to ("blas" "lapack" "cblas"). But, this doesn't explicitly state that the user has either atlas-lapack or openblas-lapack installed.
So, my goto for now:
-
change the deps to ("fftw" "blas" "lapack" "cblas")
-
add a switch to fallback to openblas-lapack if atlas-lapack doesn't exist. However, build will fail if neither of them exists.
-
manual "_use_mkl" switch to use mkl instead. This will have priority than others.
Let me know if anyone has further comments or suggestions. Thanks.
Pinned Comments
ydallilar commented on 2018-05-24 18:30
Yes, that seems to be a new feature. I was thinking about it. There are a few considerations:
1) Recently updated sextractor and scamp can use openblas instead but psfex still can't (maybe an update for psfex is on the way as well?). So, for now we should be consistent probably. For example, users who compile sextractor against openblas then need to remove openblas and install atlas-lapack to compile psfex.
2) I can change dependencies from atlas-lapack to ("blas" "lapack" "cblas"). But, this doesn't explicitly state that the user has either atlas-lapack or openblas-lapack installed.
So, my goto for now:
change the deps to ("fftw" "blas" "lapack" "cblas")
add a switch to fallback to openblas-lapack if atlas-lapack doesn't exist. However, build will fail if neither of them exists.
manual "_use_mkl" switch to use mkl instead. This will have priority than others.
Let me know if anyone has further comments or suggestions. Thanks.