Archives Discussions

[MicahVillmow]

Raistmer,
There is no responsibility for other vendors to support our vendor specific extensions, which is the first 4 errors. Looks like different calling convention issue on the 5th error.

[MicahVillmow]

We extend the cl.hpp file with our vendor extensions. If you want the unmodified standard cl.hpp file, you can get it from here:
http://www.khronos.org/registry/cl/api/1.1/cl.hpp

I've filed a bug report with the correct team about this to see if they can find a solution for the next SDK release.

[Raistmer]

Originally posted by: MicahVillmow

We extend the cl.hpp file with our vendor extensions. If you want the unmodified standard cl.hpp file, you can get it from here:

http://www.khronos.org/registr.../api/1.1/cl.hpp



I've filed a bug report with the correct team about this to see if they can find a solution for the next SDK release.

Thanks!
For now I just use older cl.hpp for NV SDK and APP SDK 2.5's own for ATi builds, but of course it would be better to have single compatible header.

[Raistmer]

I thought cl.hpp is part of Kronos header set now, that is, OpenCL standart, not vendor extension. Is it wrong? Why Kronos copyright in that header then?...