Re: On providing a separate source package for the CUDA build of a library.
Hi Ghis
On 15 December 2015 at 13:55, Ghislain Vaillant <ghisvail@gmail.com> wrote:
> Upstream kindly asked whether the CUDA backend could be packaged as well,
> and I wanted to confirm with you guys what my options are. I thought about
> providing an additional source package with the same upstream sources, but
> which would be responsible for building the CUDA backend only. I believe
> this source package (arrayfire-cuda) would have to be in contrib since it is
> open-source licensed but build-depends on non-free components (CUDA).
>
> Is this the right way to go? Are there any tips to handle the
> synchronization between the arrayfire and arrayfire-cuda packages? Any other
> examples of a set-up like this in the archive?
Have a look at starpu [1] and starpu-contrib [2].
Regards
Graham
[1] https://packages.qa.debian.org/s/starpu.html
[2] https://packages.qa.debian.org/s/starpu-contrib.html
Reply to: