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

Ghislain Vaillant ghisvail at gmail.com
Thu Jul 9 18:41:14 UTC 2015

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 ?

Suggestions / opinions welcome.


More information about the pkg-boost-devel mailing list