glXGetDriverConfig parameters do not provide a context to dynamically
check for the presence of the function, so the dispatcher directly calls
glXGetDriverConfig, but in non-dri builds dri_glx.c didn't provide
glXGetDriverConfig.
This change make it just return NULL in that case.
Fixes: 84f764a75
On 15.01.2018 15:38, Samuel Thibault wrote:
glXGetDriverConfig parameters do not provide a context to dynamically
check for the presence of the function, so the dispatcher directly calls
glXGetDriverConfig, but in non-dri builds dri_glx.c didn't provide
glXGetDriverConfig.
This change make it ju
Hi,
On 15-01-18 15:38, Samuel Thibault wrote:
glXGetDriverConfig parameters do not provide a context to dynamically
check for the presence of the function, so the dispatcher directly calls
glXGetDriverConfig, but in non-dri builds dri_glx.c didn't provide
glXGetDriverConfig.
This change make it
On 15 January 2018 at 14:38, Samuel Thibault
wrote:
> glXGetDriverConfig parameters do not provide a context to dynamically
> check for the presence of the function, so the dispatcher directly calls
> glXGetDriverConfig, but in non-dri builds dri_glx.c didn't provide
> glXGetDriverConfig.
>
> This