On 29.11.2012 21:11, Ralph Sennhauser wrote:
> On Thu, 29 Nov 2012 17:09:34 +0100
> justin wrote:
>
>> On 29/11/12 16:51, Ian Stakenvicius wrote:
> [...]
>>> ..ok remind me again what the .pc files provide you? this is so
>>> that you can have slotted blas providers and various packages can
>>>
On Thu, 29 Nov 2012 17:09:34 +0100
justin wrote:
> On 29/11/12 16:51, Ian Stakenvicius wrote:
[...]
> > ..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 th
-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
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/29/2012 05:09 PM, justin wrote:
>
> 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 p
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_LIB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
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_LIBRA
