(regression) Oxide 1.9 started using a private Qt symbols

[Timo Jyrinki]

Oxide 1.9 has gained dependencies on both qtbase-abi-5-4-2 and qtdeclarative-abi-5-4-1, please investigate how they could be dropped again.

[Chris Coulson (chrisccoulson)]

Oxide has always used private symbols (at least, from qtgui). The additional ones will be dropped when we switch to Qt 5.5 which has proper support for exposing value types to Qml.

[Chris Coulson (chrisccoulson)]

Well, it needs Qt 5.5 and also a fix for https://bugreports.qt.io/browse/QTBUG-47940

[Timo Jyrinki (timo-jyrinki)]

In 1.8.4 there was no dependency on the abi, and there wasn't also in June when Qt 5.4.2 was upgraded. The dependency can be checked (in addition to dpkg -s) by opening the DEBIAN/control of the binary deb https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-026/+build/7762777/+files/liboxideqt-qmlplugin_1.8.4-0ubuntu2_amd64.deb

In earlier times there was a dependency but it was dropped when oxideqmlscene was dropped.

At least the earlier usage was not flagged as being private symbol usage based on the Qt's symbol files, which meant Oxide did not need rebuilds when upgrading Qt. The new use in 1.9 however does bring both the qtbase and qtdeclarative abi dependencies in (https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/7877092/+files/liboxideqt-qmlplugin_1.9.1-0ubuntu1_amd64.deb) so something new of both has been started to be used.

Thanks for reporting bugs upstream.

[Timo Jyrinki (timo-jyrinki)]

Attach is the list of 22 used private symbols. 5 in qtbase and 17 in qtdeclarative.

[Chris Coulson (chrisccoulson)]

None of those are a surprise, and they'll all go away when compiling with Qt5.5 which doesn't require private APIs to expose value types to Qml.

We currently use qt_gl_global_share_context() with Qt5.4 (or QOpenGLContextPrivate::globalShareContext()) with Qt5.3. I'm surprised they aren't flagged up