On 14/12/2018 19:22, Jon Turney wrote:
On 14/12/2018 15:15, Emil Velikov wrote:
On Fri, 14 Dec 2018 at 14:56, Jon Turney
wrote:
Sadly, the GLX_USE_APPLEGL and GLX_USE_WINDOWSGL cases are not identical
(because GLX_USE_WINDOWSGL uses vtables rather than a maze of ifdefs)
Include again, as fu
On 14/12/2018 15:15, Emil Velikov wrote:
On Fri, 14 Dec 2018 at 14:56, Jon Turney wrote:
Sadly, the GLX_USE_APPLEGL and GLX_USE_WINDOWSGL cases are not identical
(because GLX_USE_WINDOWSGL uses vtables rather than a maze of ifdefs)
Include again, as functions prototyped by it are used in
the
On Fri, 14 Dec 2018 at 14:56, Jon Turney wrote:
>
> Sadly, the GLX_USE_APPLEGL and GLX_USE_WINDOWSGL cases are not identical
> (because GLX_USE_WINDOWSGL uses vtables rather than a maze of ifdefs)
>
> Include again, as functions prototyped by it are used in
> the GLX_USE_WINDOWSGL path.
>
> Make
Sadly, the GLX_USE_APPLEGL and GLX_USE_WINDOWSGL cases are not identical
(because GLX_USE_WINDOWSGL uses vtables rather than a maze of ifdefs)
Include again, as functions prototyped by it are used in
the GLX_USE_WINDOWSGL path.
Make the include guard around the __glxGetMscRate() definition match
