3 ms·

The GLX library (which is implemented in terms of Xlib data types) itself is implemented by the nvidia driver (it speaks some other driver-internal stuff to the

by evmar 14y ago

The GLX library (which is implemented in terms of Xlib data types) itself is implemented by the nvidia driver (it speaks some other driver-internal stuff to the nvidia kernel-side bits) -- as you mention, rendering is client-side these days, so the implementing GLX protocol doesn't amount to much. It is maybe still possible to use enough of of xlib+nvidia-glx in an XCB app to make things work but I think that's uncharted territory -- and it seems likely to me nvidia's glx expects you to have the other pieces of xlib around, such as using xlib's event queues.

exDM69 14y ago
> It is maybe still possible to use enough of of xlib+nvidia-glx in an XCB app to make things work but I think that's uncharted territory -- and it seems likely to me nvidia's glx expects you to have the other pieces of xlib around, such as using xlib's event queues. I've done XCB+Xlib+GLX + proprietary graphics drivers, it does work although it's sort of uncharted territory but if you're brave you can make it work. Initialize Xlib as usual, then use XSetEventQueueOwner to enable handling events with XCB and finally do you GLX stuff with the Xlib Display object.
- stevenlstarr 14y ago
  That was part of my point I have stacks of xlib and glx books/docs xcb's documentation is severely lacking. I want to write my desktop not fool around with xlib here and xcb there I am getting old and would like to see Desktop Linux as a major player in my life time. I just want something concrete xlib and glx for now gives me that. When wayland is stable enough and has hardware acceleration for nvidia's binary blobs then Ill move on to that. I dont want to put all my eggs in one basket on something that might happen. Nvidia needs to just come out and say yes if wayland proves fruitfull we will support it.
  - evmar 14y ago
    I know this opinion may be unpopular, but: people have been successfully writing xlib apps for literally decades. There's no reason to use xcb for that type of app, especially if you're just trying to get a GL window on the screen and you don't expect to be doing lots of tricky X calls.

by evmar 14y ago

exDM69 14y ago

> It is maybe still possible to use enough of of xlib+nvidia-glx in an XCB app to make things work but I think that's uncharted territory -- and it seems likely to me nvidia's glx expects you to have the other pieces of xlib around, such as using xlib's event queues. I've done XCB+Xlib+GLX + proprietary graphics drivers, it does work although it's sort of uncharted territory but if you're brave you can make it work. Initialize Xlib as usual, then use XSetEventQueueOwner to enable handling events with XCB and finally do you GLX stuff with the Xlib Display object.

stevenlstarr 14y ago
That was part of my point I have stacks of xlib and glx books/docs xcb's documentation is severely lacking. I want to write my desktop not fool around with xlib here and xcb there I am getting old and would like to see Desktop Linux as a major player in my life time. I just want something concrete xlib and glx for now gives me that. When wayland is stable enough and has hardware acceleration for nvidia's binary blobs then Ill move on to that. I dont want to put all my eggs in one basket on something that might happen. Nvidia needs to just come out and say yes if wayland proves fruitfull we will support it.
- evmar 14y ago
  I know this opinion may be unpopular, but: people have been successfully writing xlib apps for literally decades. There's no reason to use xcb for that type of app, especially if you're just trying to get a GL window on the screen and you don't expect to be doing lots of tricky X calls.