On 05/20/2014 12:21 PM, Chad Versace wrote:
On Tue, May 20, 2014 at 10:18:50AM -0700, Stéphane Marchesin wrote:
On Tue, May 20, 2014 at 9:14 AM, Brian Paul wrote:
It seems unusual for a new extension to be defined in its own header file
rather than the eglext.h file.
Is ther
On Tue, May 20, 2014 at 10:18:50AM -0700, Stéphane Marchesin wrote:
>
>
>
> On Tue, May 20, 2014 at 9:14 AM, Brian Paul wrote:
>
> It seems unusual for a new extension to be defined in its own header file
> rather than the eglext.h file.
>
> Is there a particular reason for that?
On Tue, May 20, 2014 at 9:14 AM, Brian Paul wrote:
> It seems unusual for a new extension to be defined in its own header file
> rather than the eglext.h file.
>
> Is there a particular reason for that? Are there other vendors putting
> their extensions in new header files like this?
>
>
The rea
It seems unusual for a new extension to be defined in its own header
file rather than the eglext.h file.
Is there a particular reason for that? Are there other vendors putting
their extensions in new header files like this?
-Brian
On 05/16/2014 04:05 PM, Chad Versace wrote:
Ian and Brian,
Ian and Brian,
How do you feel about importing this EGL extension header from the
Chromium source tree? Do you prefer to import the header or just add its
content to eglmesaext.h?
I have a slight preference for importing the header.
-Chad
On Tue, May 06, 2014 at 12:10:56PM -0700, Sarah Sharp wr
In order to support the (currently unregistered) Chromium-specific EGL
extension eglGetSyncValuesCHROMIUM on Intel systems, we need to import
the Chromium header that defines it. The file was downloaded from
https://chromium.googlesource.com/chromium/chromium/+/trunk/ui/gl/EGL/eglextchromium.h
I
