Description of problem:
GstGL in Rawhide's gstreamer1-plugins-bad-free is built with only desktop OpenGL support. But Samsung's Chromium GStreamer backend (which I am also trying to backport to QtWebEngine) needs GstGL built with OpenGL ES support (even on desktop platforms). It should be possible to build it with support for both.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Check out qt5-qtwebengine from dist-git.
2. Switch to the gstreamer branch.
3. Try to build that branch for Rawhide.
error: #error "GstGL with GLES2 support is required"
The build succeeds, or proceeds far enough to uncover some issue in my package rather than in GStreamer.
The way Chromium uses GstGL is that it renders using OpenGL ES, sends the OpenGL ES instructions over across IPC, and lets the GPU process convert that to whatever OpenGL the machine natively uses using ANGLE. That is why it always needs OpenGL ES support in GstGL, even on desktop platforms. (But the current gstreamer1-plugins-bad-free specfile doesn't even enable OpenGL ES on ARM.)
Created attachment 1128806 [details]
Fix FTBFS, #1295444, #1267665, #1308290
The attached patch fixes this bug, bug #1295444, bug #1267665 and the FTBFS of the current Rawhide specfile.
Please note that this RFE is just a matter of adding a BuildRequires: mesa-libGLES-devel. GstGL builds fine with BOTH desktop OpenGL and OpenGL ES support.
gstreamer1-plugins-bad-free-1.9.1-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-a1bc3f1930
gstreamer1-plugins-bad-free-1.9.1-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-a1bc3f1930
gstreamer1-plugins-bad-free-1.9.1-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.