oxide-qt fails to build against Qt 5.4.0

Because of https://qt.gitorious.org/qt/qtbase/commit/219c2eb4e28dd1c806cbc2115ff40454d6d3f9c5

It will also affect the webbrowser-app/webapp-container and ubuntu-system-settings-online-accounts (that also use the private header)

It seems the actual removal commit https://codereview.qt-project.org/#/c/97487/ was a couple of days after the beta release.

When fixing the problem, please do a conditional fix with #if QT_VERSION < QT_VERSION_CHECK(5, 4, 0) so that you can ship the fix already before Qt 5.4 lands. It makes Qt landings less complex if no-change rebuilds are possible.

Providing the Oxide functionality to fix bug #1387537 would mean webbrowser/online-accounts would not need to be touched or even included in the Qt landings (they would continue to work with new Qt without a rebuild).

UI Toolkit has a fix for this in the following MP: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/newOpenGlPrivates/+merge/243373. You can probably just use a similar landing (please attach a patch already before your landing so that I can try it out in the PPA).

Changing QOpenGLContextPrivate::setGlobalShareContext(shareContext.data()); to qt_gl_set_global_share_context(shareContext.data()); and additionally QOpenGLContextPrivate::globalShareContext() to qt_gl_global_share_context() were enough and I was able to build Oxide against Qt 5.4.0.

1.5 seems to have fixed only qt/tests/qmltests/main.cc while qt/qmlrunner/main.cc remains unfixed.

Is qt/quick/oxide_qquick_init.cc ok with its "oxide::qt::EnsureChromiumStarted"?

Attached is the patch I used for 1.4, patching three places.

Fixed a different way: http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/950

Fix released https://launchpad.net/ubuntu/+source/oxide-qt/1.5.3-0ubuntu2