When Cloo assembly is loaded by the application, it automatically tries to load OpenCL.dll from the host operating system. This hapens when the application is being loaded, and no code has been executed yet.
When a computer does not have OpenCL support, Driver's OpenCL.dll is missing, and the application simply crashes because it can't find the assembly.
The expected behavior would be that OpenCL (or is this OpenTK responsability?) to do a late binding of the OpenCL dll, and in case OpenCL.dll is not found, simply return zero OpenCL Platforms and devices.
Log in to post a comment.