[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#675528: ITP: ocl-icd -- Generic OpenCL ICD Loader



On 2012-06-02 00:38, Vincent Danjean wrote:

>   So, is it possible to upload opencl-headers to main instead of
> contrib?

Package updated and upload requested ...


> This source package will provide two binary pakages:
> Package: ocl-icd-libopencl1
> Description: Generic OpenCL ICD Loader
>  OpenCL (Open Computing Language) is a multivendor open standard for
>  general-purpose parallel programming of heterogeneous systems that include
>  CPUs, GPUs and other processors.
>  .
>  This package contains an installable client driver loader (ICD Loader)
>  library that can be used to load any (free or non-free) installable client
>  driver (ICD) for OpenCL. It acts as a demultiplexer so several ICD can
>  be installed and used together.

If that is compatible with all the implementations, couldn't we just
call it libopencl1? (+Conflicts/Replaces: libopencl1)
And there should be a corresponding libopencl1-dev package, too.
As that's probably what users need for their OpenCL applications.

> Package: ocl-icd-dev
> Description: Development files to build a ICD Loader
>  OpenCL (Open Computing Language) is a multivendor open standard for
>  general-purpose parallel programming of heterogeneous systems that include
>  CPUs, GPUs and other processors.
>  .
>  This package provides a header file that allows a OpenCL implementation
>  to build a installable client driver (ICD). With a ICD, an OpenCL
>  implementation can be used by any OpenCL program without the need
>  to link the program to the specific OpenCL implementation.
Add something like:
  .
  For building OpenCL applications install the libopencl1-dev package
instead.

> A few word about the context. There exist lots of OpenCL implementations.
> A OpenCL program can either link to a specific OpenCL implementation
IIRC there is non of these packaged in Debian

> or it can link to a standardized libOpenCL library that allows the
> program to dynamically choose the OpenCL implementation or even to
> use several OpenCL implementations in the same program. In fact
> libOpenCL is only a wrapper (more exactly a dispatcher) to
> OpenCL implementations provided as ICD.
currently nvidia-libopencl1 [non-free] and amd-libopencl1 [non-free]
available - eventually these could be phased out in favor of a free one


Andreas



Reply to: