Rolf Eike Beer wrote
> Yes, but the preferable solution would be that you ship a
> OpenBLASConfig.cmake
> with your installation, so it would work with any CMake version and you
> can
> adapt that file yourself in case of new components, library locations or
> other
> things.
Why would OpenBLAS have to do this, when none of other BLAS implementations
supported by FindBLAS.cmake aren't?
OpenBLAS is probably the most convenient open source BLAS implementation to
use at the moment, plus very fast, and it would really make every sense to
have it supported by CMake. Furthermore, I think rather simple change to
FindBLAS.cmake is needed to support it: basically, as OpenBLAS is derived
from Goto BLAS implementation, probably Goto BLAS related segment of
FindBLAS.cmake should be just duplicated, with "Goto" changed to "OpenBLAS",
and "goto2" changed to "openblas". On the other side, same type of addition
would be needed for FindLAPACK.cmake, as OpenBLAS is implementing LAPACK too
(also through libopenblas.{a,so} library).
Thanks.
--
View this message in context:
http://cmake.3232098.n2.nabble.com/Support-OpenBLAS-in-FindBLAS-module-tp7588937p7588979.html
Sent from the CMake mailing list archive at Nabble.com.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
