OpenGL on Wayland
kalrish.antrax at gmail.com
Fri Jun 27 12:54:48 PDT 2014
I've catched the mouse. As my graphics card is on the r200 driver, which
supports OpenGL 1.3 or 1.4, I used the LLVMpipe driver for my project,
because it supported much modern versions. However, software EGL/libGL does
not support the EGL_KHR_create_context extension, warning:
libEGL debug: bad context attribute 0x30fd *(EGL_CONTEXT_MINOR_VERSION,
> which had been set to 3 to get OpenGL 3.3)*
With the OpenGL module I have just written, if I omit the minor version
flag to make EGL accept it, I am getting an OpenGL ES 3 context. AFAIK,
LLVMpipe supports 3.3, but how can such a context be created?
On Fri, Jun 27, 2014 at 9:26 PM, Kalrish Bäakjen <kalrish.antrax at gmail.com>
> On Fri, Jun 27, 2014 at 9:15 PM, Jason Ekstrand <jason at jlekstrand.net>
>> The issue everyone talks about is that libGL also contains a GLX
>> implementation so it links against Xlib. This will create a link-time
>> dependency on Xlib. However, since your application will not be making any
>> GLX calls, those code-paths will never get exercised and it will gave no
>> runtime dependency on having an X server. Really, this is a packaging
>> problem far more than it is a programming problem.
> Oh... Sorry for the noise, then. I will look at it again, and reply with
> my results later.
> I suspect I didn't load some function with eglGetProcAddress(). If, as
> mentioned in the slides, libGL exposes 1.4, it could well be the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wayland-devel