User needs libCL to use OpenCL, to do anything useful you need to compile kernels (shader programs) using libCLC (CL Compiler). Though technically a pre-compiled shader could be loaded without the need of libCLC I'm not sure if the Vivante libraries actually support this (to pull the objects back out from libCLC). The fact that libCL silently fails compilation when libCLC is missing is what would lead me to consider both are required for OpenCL.
On 2013-06-20, at 3:53 PM, Otavio Salvador <[email protected]> wrote: > On Mon, Jun 17, 2013 at 12:33 PM, Sébastien Taylor <[email protected]> wrote: >> The issue is dependency between the Vivante OpenCL libraries that isn't >> implicit. If the libCLC.so isn't found the compilation simply fails every >> time. I understand that it makes sense to separate the CL and CLC libraries >> as one might want to use pre-compiled .cl files but the silently failing is >> an issue. This is all of course all Vivante and uncontrollable by Yocto. >> As far as Yocto is concerned libCL.so and libCLC.so should probably be >> considered interdependent by default. >> >> If not familiar with OpenCL, when I refer to compilation I mean run-time >> compilation of the .cl kernels. > > I am not used to OpenCL but I'd like to understand how it should be > properly package so this is done in a logical way. > > Can you please provide me an example of: > > * when user needs libCL > > * when user needs libCLC > > * when user needs /both/ > > ? > > Regards, > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.br http://projetos.ossystems.com.br > Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
