![]() ![]() The vendors' SDKs provide a multitude of tools and support libraries: opencl-headers: OpenCL C/C++ API headers.ocl-icd: OpenCL ICD loader implementation, up to date with the latest OpenCL specification.Developmentįor OpenCL development, the bare minimum additional packages required, are: ICD loaders are vendor-agnostic and may be used interchangeably (as long as they are implemented correctly). Note: ICD Loader's vendor is mentioned only to identify each loader, it is otherwise completely irrelevant. Provides OpenCL 2.0, deprecated in favour of intel-compute-runtime. The available packages containing various OpenCL ICDs are: This is necessary because all the SDKs add their runtime's lib directories to the search path through ld.so.conf.d files. If you want to ensure the ICD loader from the ocl-icd package is used, you can create a file in /etc/ld.so.conf.d which adds /usr/lib to the dynamic program loader's search directories: The other ICD loader libraries are installed as part of each vendor's SDK. Unfortunately, most vendors do not provide completely up-to-date ICD loaders, and therefore Arch Linux has decided to provide this library from a separate project ( ocl-icd) which currently provides a functioning implementation of the current OpenCL API. Most OpenCL vendors provide their own implementation of an OpenCL ICD loader, and these should all work with the other vendors' OpenCL implementations. The OpenCL ICD loader is supposed to be a platform-agnostic library that provides the means to load device-specific drivers through the OpenCL API. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |