On 09/01/16 08:35, Martin Uecker wrote:
Ghislain Vaillant :
FYI, the same trick is used for other dependencies with multiple
backends such as OpenCL.
What is the state of OpenCL on Debian?
The OpenCL headers are regularly updated, so are the main open-source
drivers
On 09/01/16 08:35, Martin Uecker wrote:
Ghislain Vaillant :
FYI, the same trick is used for other dependencies with multiple
backends such as OpenCL.
What is the state of OpenCL on Debian?
The OpenCL headers are regularly updated, so are the main open-source
drivers
On 09/01/16 08:03, Martin Uecker wrote:
What are the next steps?
Submit an RFS bug [1] and upload the package to mentors [2].
That's the usual route. Maybe the MoM process is different though. To be
checked with Andreas.
[1] http://mentors.debian.net/sponsor/rfs-howto
[2]
Hi,
On Sat, Jan 09, 2016 at 10:46:45AM +, Ghislain Vaillant wrote:
> On 09/01/16 08:03, Martin Uecker wrote:
> >What are the next steps?
>
> Submit an RFS bug [1] and upload the package to mentors [2].
In the Debian Med team we simplify this. A mail here on the list where
you announce that
Hi,
no further comments to the OpenCL question which is IMHO fully answered
(way better than I could since I have no experience in this field).
There are three remaining and easy to fix lintian issues:
I: bart source: duplicate-short-description bart libbart-dev
N:
N:The listed binary
Hi Ghislain,
Ghislain Vaillant :
> On 08/01/16 19:29, Martin Uecker wrote:
> Good. Then, you might want to use libbart-dev as the package name, which
> is usually the naming convention for packages containing any libraries
> (in shared or static form).
Done.
> > Also
Ghislain Vaillant :
>
> FYI, the same trick is used for other dependencies with multiple
> backends such as OpenCL.
What is the state of OpenCL on Debian?
We only support CUDA in BART, but I always wanted to add OpenCL
support and it should be fairly easy...
Martin
7 matches
Mail list logo