It seems that most packages that I use do not reference a blas header directly. They forward declare the functions they need directly, and add the appropriate suffix (_) to account for whether the blas is fortran or c. This requires user knowledge of the calling conventions of the blas library they are accessing.
In addition, the packager of the reference blas, at least on SUSE linux, made the unfortunate decision to name the reference blas shared and static libraries by the exact same name, libblas. Is it possible with the 2.6 series of cmake to enforce that the correct version of the blas is linked in this situation? If I remember correctly cmake 2.4 can get this wrong? Regards, Juan On Mon, Jul 21, 2008 at 7:21 AM, Alin M Elena <[EMAIL PROTECTED]> wrote: > Hi, > > I try to rewrite a module BLAS. > > After an analysis I realised that find_package as it stands now may not be > enough for the functionality that I need. > > for BLAS it happens to be found in many forms supplied by different vendors. > So I thought that an optional argument Vendor would be useful. > > Another issues is deciding what you want: static or dynamic linkage. > > This is an old discussion and some solution were suggested on the list. > > To make it portable again would be useful if inside the Findxxx.cmake you > know what kind at linkage the user wants. > > Again some methods were presented on the list but they need running external > tools. I would suggest an optional parameter STATIC for find_package. > > Alin > > -- > > ______________________________________________________________________ > > "...if the universities will not study useless subjects, who will?" > > G. F. Fitzgerald, Nature, 45/46, 392 (1892) > > ______________________________________________________________________ > > Mr. Alin M. ELENA > > Atomistic Simulation Centre > > School of Mathematics and Physics > > Queen's University Belfast > > Office: +44 (0)28 9097 1428 > > Fax: +44 (0)28 9097 5359 > > http://titus.phy.qub.ac.uk/group/Alin/ > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > ______________________________________________________________________ > > _______________________________________________ > CMake mailing list > [email protected] > http://www.cmake.org/mailman/listinfo/cmake > _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
