I figured we could use some more Qt modules, so I packaged up a couple. Qt3d
bundles assimp and I'm still working on unbundling that, and even so I'm not
happy about how it references another graphics library, so that one is going
to need some more time. I also haven't looked at qtwebengine, since it bundles
chromium. Of the remaining, qtwebview depends on qtwebengine, qtactiveqt is
windows only, and I didn't look at qt{android,mac,windows}.While I was working on them, I realized that the test suite wasn't really being run. I patched qtsvg to run the test suite (and therefor propagate to all the other qt modules), but everything started breaking, due to network tests, javascript dependencies, etc., so I've moved that to a separate branch locally to work on more later. However, I do think it would be be better to enable the tests in qtsvg and then disable them on most of the modules, so that way they're ready to be fixed and enabled without waiting for me to get around to it. Thoughts? Efraim Flashner (9): gnu: Add qtdeclarative-render2d. gnu: Add qtserialbus. gnu: Add qtgamepad. gnu: Add qtscxml. gnu: Add qtpurchasing. gnu: Add qtcanvas3d. gnu: Add qtcharts. gnu: Add qtdatavis3d. gnu: Add qt3d. gnu/packages/qt.scm | 189 +++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 188 insertions(+), 1 deletion(-) -- 2.11.0
