On 27 June 2013 21:19, scl <scl gplus gmail com> wrote:
On 27.06.13 at 09:15 AM Alberto Mardegan wrote:Hi Jon,
Hi all!
I don't know when (or even "if") I'll start working on that, but I'm
considering extending the gegl Qt bindings to include almost everything
which is currently available to the C/glib bindings, so that a developer
writing an application using gegl in Qt wouldn't have to use the C/glib
API at all.
as it seems some movement is coming back to that project.
If you want to track the current building state, you can look at
https://gimptest.flamingtext.com:9090/view/GEGL/job/gegl-qt-distcheck-master/
Hi Sven,sorry for the project not being in a CI-friendly state at the moment.I am in the middle of a critical project at work, doing 60 hour+ weeks, and will be until end of next week.So not sure if I will find time to fix up your comments before that.Anyone who wants to fix up the things underneath before I get to it have my full blessing to push the fixes directly to master.With that being said, it would be nice if the Jenkins job could also trigger on a "for-master", "integration" or "test" branch, if people would like to test their changes outside of master.1)
Currently the project depends on GEGL 0.2, the latest GEGL master branch has version 0.3. I don't know whether gegl-qt will work with it, so I leave it up to you to update the gegl-qt project. Let me know
if you update it, so I can update the Jenkins build job.Yes, it needs updating before that change can be made.2)
Another thing it that error 'qml-paint.cpp:19:42: fatal error: examples/common/paint-engine.h: No such file or directory' that breaks
the build. Can you fix it to make the new contributor able to work
on that project?This is likely an easy fix. I suspect that the problem is merely the file not being distributed in the tarball, or that the directory is not on the include path when the examples are built from the tarball.