Tom Stellard writes:
> The build was failing because the official CL headers have a few defines,
> like:
>
> \# define cl_khr_gl_sharing 1
>
> Which have the same name as some class members of clang's OpenCLOptions class.
> If we include the cl headers first, this breaks the build because the me
On 07/20/2016 11:46 AM, Tom Stellard wrote:
The build was failing because the official CL headers have a few defines, like:
\# define cl_khr_gl_sharing 1
Which have the same name as some class members of clang's OpenCLOptions class.
If we include the cl headers first, this breaks the build beca
The build was failing because the official CL headers have a few defines, like:
\# define cl_khr_gl_sharing 1
Which have the same name as some class members of clang's OpenCLOptions class.
If we include the cl headers first, this breaks the build because the member
names of this class are replace
On Tue, Jul 19, 2016 at 11:13 AM, Tom Stellard wrote:
> The build was failing because the official CL headers have a few defines,
> like:
like ...
>
> Which have the same name as some class members of clang's OpenCLOptions class.
> If we include the cl headers first, this breaks the build becau
The build was failing because the official CL headers have a few defines, like:
Which have the same name as some class members of clang's OpenCLOptions class.
If we include the cl headers first, this breaks the build because the member
names of this class are replaced by the literal 1.
---
.../st
