Apologies for the new thread, I just subscribed in order to comment on this, and didnt know how to reply in the existing thread.
I am grateful to Xianyi for his addition of OpenBlasConfig.cmake, and I do recognize that this is the direction that projects should go when wanting to build CMake support for their users. The issue, as cgorac points out, is that other projects (LAPACK in this case) use FindBLAS.cmake inside their FindLAPACK.cmake files. So, in order to get FindLAPACK.cmake to work with OpenBLAS, it would require that the developers that maintain FindLAPACK.cmake change that file. The same would have to happen for any other projects that use FindBLAS.cmake. In short, CMake already has a “blessed” set of BLAS implementations (MKL, Intel, Goto, etc.), and it would be easier for users of LAPACK (and users of projects that use BLAS), if OpenBLAS were included in this set of CMake “blessed” BLAS implementations. Of course, OpenBLAS would still be happy to provide OpenBlasConfig.cmake (I am guessing) for users of OpenBLAS directly. Best Regards, Rob
-- 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
