-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 29/11/12 11:09 AM, justin wrote: > On 29/11/12 16:51, Ian Stakenvicius wrote: >> On 29/11/12 09:56 AM, justin wrote: >> >>> Standard autotools based packages always use >> >>> --with-blas= >> >>> so it is pretty simple for us to make it to >> >>> --with-blas="$(pkg-config --libs blas)" >> >>> same thing goes for cmake and >> >>> -DBLAS_LIBRARIES="$(pkg-config --libs blas)" >> >>> This game has been played since ever, because blas/lapack are >>> bundled in more then 80% of the packages using it. So we are >>> used to patch them to use system libs. So why not making our >>> lives easier by having a pkg-config option? >> >>> justin >> >> >> ..ok remind me again what the .pc files provide you? this is so >> that you can have slotted blas providers and various packages can >> choose their preferred one instead of having to use the eselected >> one? or... >> >> >> >> >> > > Not exactly. The user can choose for each package newly by > eselecting the wanted implementation. This is the user side. From > the pm side we ensure that the choice is really respected by > linking against package specific names [1] instead of the generic > ones e.g. libblas.so. And this can be achieved in an easy way by > using pkg-config. > > justin > > 1) # eselect blas set atlas-threads # pkg-config --libs blas > -lptf77blas -lm -latlas -lpthread > > # eselect blas set reference # pkg-config --libs blas -lrefblas > >
Doing this via an eclass that would export BLAS_LIBS and BLAS_CFLAGS (and appending necessary equivalents to mycmakeargs) for src_configure based on what is eselected wouldn't be as easy or easier to do? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlC3kPMACgkQ2ugaI38ACPCa7gD+M7knL7yghfUe6oejohgV/upw iDJmpCkt5WDZVoqu76EBAJGvMG1TgebSWreHx9RPdXc2RErstr7Cfg0ulfCy/WJ8 =uuBE -----END PGP SIGNATURE-----
