[pkg-boost-devel] Fwd: Packaging of boost.compute

Dimitri John Ledkov xnox at debian.org
Tue Jul 14 22:02:39 UTC 2015


On 9 July 2015 at 19:41, Ghislain Vaillant <ghisvail at gmail.com> wrote:
> Hi all,
>
> On 15/06/15 04:19, Steve M. Robbins wrote:
>>
>> On June 9, 2015 10:14:54 AM Ghislain Vaillant wrote:
>>
>>> As far as I am aware, only ArrayFire requires Boost.Compute. It is
>>> required in order to build its OpenCL backend, alongside other build
>>> -dependencies like clBLAS and clFFT, which I am also in charge of
>>> packaging. Meanwhile, the CPU backend of ArrayFire is already
>>> operational.
>>>
>>> Since it will take some time to get the other OpenCL bdeps in sid, I am
>>> thinking about uploading a package with ArrayFire with CPU backend only
>>> at first, and later add the OpenCL backend packages once the bdeps are
>>> available in sid.
>>>
>>> The question I had in mind was whether it makes sense to propose both
>>> clBLAS and clFFT plus Compute, or leave Compute out considering that,
>>> by the time clBLAS and clFFT are uploaded to Debian (they are ready for
>>> submission), Boost 1.59 *may* be already out. Thoughts ?
>>
>> That seems like a reasonable plan, to me.
>>
>> -Steve
>>
>>
>
> Both clBLAS and clFFT are now in sid, which happened much faster than I
> originally expected. That means only Boost.Compute is missing in order to
> build the OpenCL backend for ArrayFire.
>
> Would that be ok if I uploaded a standalone compute source package
> (perhaps based on Kyle's PPA, as he kindly suggested) and make ArrayFire
> bdep on libboost-compute-dev >= 1.59 | libcompute-dev ?
>

Is there a stand alone git repository for compute component already
and is it compatible with boost1.58? I'm happy to included as a
multi-tarball component in an 1.58 upload under libboost-compute-dev
name already.

Point me to its git repository and I'll take a look.


-- 
Regards,

Dimitri.



More information about the pkg-boost-devel mailing list