On Wed, Jun 2, 2010 at 2:08 PM, Michael Wild <[email protected]> wrote: > > Just to correct a thing: cblas_dgemm is NOT an implementation detail, it is > part of CBLAS which is the official C-interface to BLAS.
I think "implementation detail" mentioned in the OP message was not about CBLAS per se, but about linking C code from the Fortran compiler instead, which is indeed an implementation detail, and which is surfacing because of FindBLAS.cmake is currently working exactly by asking Fortran compiler to find a CBLAS function - so much more meaningful test would be to ask the compiler to find BLAS function, again exactly as suggested in the OP message. As far as your idea on splitting FindBLAS into multiple modules: this kind of arrangement makes sense too, but basically all the provisions for this type of modularization, as well as for selecting particular BLAS implementation, are already there in existing FindBLAS module - so it's only a question of one or another type of module organization. This module is indeed very complex, but so are number of other CMake modules. Obviously, no maintainer of these modules could afford to track all of the possible implementation, but basically users of particular implementation are usually reporting errors and suggesting improvements, and this worked very well so far. It seems only in this particular case that the issue somehow got below of the radar of Kitware people, hope they would fix it now... Regards. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
