Bug#629518: Preliminary AMD APP SDK Packaging
On 2011-06-16 10:05, Tomasz Rybak wrote:
> Thanks.
> I was able to build it offline (only 64-bit versions, as I did
> not have 32-bit libraries installed).
>
> Currently amd-app-sdk-dev does not build. Will it be just meta-package
> depending on all AMD APP-related packages?
I'm not yet sure what to put into this package ...
> lintian complains about:
> W: amd-libopencl1: package-name-doesnt-match-sonames libOpenCL1
I hope some vendor would release a free version of these libraries -
like nvidia did with libvdpau1. It's just a generic wrapper, not an
implentation.
> At the same time I was not able to install amd-libopencl1:
> Translation - both nvidia-libopencl1 and amd-libopencl1 provide
> libopencl1 and as nvidia-libopencl1 is properly installed
> dpkg will not install amd-libopencl1.
libopencl1 is just a generic loader and can use any implementation (the
icd packages).
> But thanks to having /usr/lib/libamdocl64.so in amd-opencl-icd
> python-pyopencl was able to detect and use OpenCL implementations
> from both NVIDIA and AMD. So current situation makes sense
> and works for my packages.
Unfortunately nvidia and amd implementations are not identical (symbol
versioning etc.) and the amd one seems to work a bit better with amd
than nvidia-libopencl1. nvidia icd seems to work the same with both
implemntations. (the oclinfo program from amd crashed at some point with
nvidia-libopencl1)
> By current situation I mean nvidia-opencl-icd providing
> opencl-icd and depending on nvidia-libopencl1, and amd-opencl-icd
> providing opencl-icd and containing AMD OpenCL implementation.
> As long as I can install more than one ICD and all of them work
> I am content.
That was the idea behind OpenCL and my packaging.
> Would it make sense to have similar meta-package for opencl-dev?
> This way if I have NVIDIA hardware I install nvidia-opencl-dev
> (providing, say, opencl-dev), and if I have AMD/ATI hardware
> I install amd-opencl-dev (or amd-app-sdk) which also can provide
> opencl-dev meta-package.
May be a good idea. But finally we would need some shlibs magic to map
the dependency on <vendor>-libopencl1 to libopencl1.
Andreas
Reply to: