OpenCL

I have to admit, my motivation to work on my personal software projects, to program anything at all, has been languishing--much like the current state of /prog/. In fact, it's been several weeks since I last touched even a line of code outside of work. It's time to dive in and do something about it.

I've decided I want to revisit my roots, but with a new twist. I'm planning to do some low-level graphics programming, but with a high-performance parallel compute language that runs on GPUs. I'm probably going to go with OpenCL. If I can get anywhere with it, I may even return to doing some demo coding.

Does anyone know how well OpenCL interoperates with OpenGL? Ultimately, I want to do my rendering to an OpenCL image2d_t object and then display that to a display adapter in real-time using OpenGL somehow. Do I manually copy it over to a dynamic GL texture object and then render a full-screen quad with it, or are the interop API calls I can use?

Yes, I could most definitely use google and solve this on my own, but I figure I might as well ask here in some half-desperate attempt to breathe life back into this board.

>>3
His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker."
It only took 20 years for someone to come up with that. It'll probably take another 10-20 for people to realize GUI applications should be written in managed languages, and another 10 to realize OOP is not a public class OOP implements Panacea.

It takes probably less time to rewrite fucking everything on your own than to convince people to help you.

Now back to the actual thread of discussion, Wayland is bound to become popular since Ubuntu is apparently going to use it. I hope it doesn't turn out to be a fiasco, just like PulseAudio.