Hmm… .Good… but how do you link your OpenCL application to different implementations that export the same set of symbols…? Thats what my initial problem was… Any idea on this?
You link to OpenCL.lib which you can find in any vendors’ SDK and is not vendor-specific. It leads to OpenCL.dll which, during initialization I presume, asks Windows registry what vendor .dlls are available (ex. nv_opencl.dll or something). Then it routes calls to particular vendor .dlls depending on platform id. I think.
You don’t link to different implementations, you statically link to OpenCL.dll which dynamically links to vendor implementations under the hood.