[Development] Future of QtOpenCL

Laszlo Papp lpapp at kde.org
Sat Jun 29 19:40:00 CEST 2013

On Sat, Jun 29, 2013 at 8:00 PM, Sebastian Lehmann <qt at leemes.de> wrote:

> Hello Qt developers,
> I'm sadly noting that the QtOpenCL project [1] is dead since end 2010,
> yet it's still
> usable. I want to bring this module back to life. Currently, the
> module has a couple of
> issues such as const-correctness and missing support for Qt5.
> I see two options with that: Either rewriting the whole module with a
> new design, or
> improving the existing code base.
> Also, I'd love to have some basic, generic and reusable algorithms
> implemented in OpenCL
> and available with an interface similar to QtConcurrent. This could be
> in a separate
> module. I have some nice ideas for the design of this.
> Some people say that there's no big advantage in having a QtOpenCL
> module, as everything
> can also be done with CL library function calls.

It is good to have a choice, at least!

> But both the
> advantage of RAII as well
> as having a Qt'ish interface are a huge help when writing applications
> with a lot of
> GPGPU computations, as the raw CL functions are way too painful to
> write (and read).
> How's your opinion about bringing QtOpenCL back to life (especially in
> Qt5)? Any concrete
> ideas or suggestions?


Disclaimer: I am not a maintainer, but I was also thinking of contributing
1-2 patches in that area. There were always other toys to play with though.

I am sure, Sean for instance will support such a playground project as a
(Qt3D) maintainer.

> Anyone out there who wants to help? How is the typical "workflow" for
> new modules in Qt5?


Many thanks,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130629/859337dd/attachment.html>

More information about the Development mailing list