Closed haasn closed 2 years ago
When using --mx the GladGLContext contains a struct member called just MemoryBarrier, from glMemoryBarrier.
--mx
GladGLContext
MemoryBarrier
glMemoryBarrier
This conflicts with the MemoryBarrier macro defined in <winnt.h>, leading to compilation issues in some cases.
<winnt.h>
It might be possible to work-around this on my end but I fear that the <winapifamily.h> import inside glad pulls this symbol in. I'll investigate.
<winapifamily.h>
Oh, actually, I think the trick is to #undef it before importing glad/gl.h, not after, as I was currently doing. That seems to have worked around it. :shrug:
#undef
glad/gl.h
When using
--mx
theGladGLContext
contains a struct member called justMemoryBarrier
, fromglMemoryBarrier
.This conflicts with the
MemoryBarrier
macro defined in<winnt.h>
, leading to compilation issues in some cases.It might be possible to work-around this on my end but I fear that the
<winapifamily.h>
import inside glad pulls this symbol in. I'll investigate.