Current path not a default include directory for clBuildProgram?

Current path not a default include directory for clBuildProgram?

Hi, I ran into a problem with the Intel 2013 R3 OpenCL SDK where a header file in the current directory was not being included in the kernel source file when calling clBuildProgram without any build options.  I had to pass "-I ." as a build option for the header file to be found and included, which everything worked fine thereafter.  Is this suppose to be required, considering it's not necessary to specify to gcc or msvc the current path as an include path?

2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi Sean,

Just note, that gcc and msvc are executed on developers machine while clBuildProgram on end user machine. The difference is security.

Leave a Comment

Please sign in to add a comment. Not a member? Join today