diff options
author | Mart Raudsepp <leio@gentoo.org> | 2020-01-04 00:39:45 +0200 |
---|---|---|
committer | Mart Raudsepp <leio@gentoo.org> | 2020-01-04 00:48:14 +0200 |
commit | 3ba0cdea3eae7b69ade6cdc94066754d562e5785 (patch) | |
tree | 1f77b308b86210212c4ff74946fa305a84fc1901 /dev-util/kdbg/Manifest | |
parent | app-portage/repoman: Remove old versions (diff) | |
download | gentoo-3ba0cdea3eae7b69ade6cdc94066754d562e5785.tar.gz gentoo-3ba0cdea3eae7b69ade6cdc94066754d562e5785.tar.bz2 gentoo-3ba0cdea3eae7b69ade6cdc94066754d562e5785.zip |
net-libs/webkit-gtk: Unconditionally build WebGL with enabled OpenGL
Building with ENABLE_GL but without WEBGL is unsupported upstream and has
no real benefits. The WebGL support can be disabled at runtime, if
desired. Therefore tie the choice of WebGL support to having enabled
GL support (full opengl or gles2), matching what upstream does if an
explicit ENABLE_WEBGL _private_ configuration value isn't given. We keep
it as a separately passed arg for now just for the sake of being explicit.
WebGL has been fine without gstreamer for a while now - that seems to
have been a temporary bug in the ancient 2.10 series - so all this does
not mean that gstreamer is required with GL and the REQUIRED_USE that
was there is dropped (not only due to IUSE=webgl going away - had it
stayed, the restriction was wrong with USE=webgl being there too).
It should also be fine without libXcomposite and libXdamage on wayland-only
builds, so those deps are simply dropped (they are still there for USE=X).
This may have been a reason some may have wanted to disable WebGL for
wayland-only builds, but it was probably legacy wrong deps.
Update a comment about WebRTC (upstream is using libwebrtc instead of
OpenWebRTC right now, but isn't a supported build option out of tarballs,
plus it may end up using gstreamer instead before it becomes non-experimental).
Also remove outdated comment about FTL_JIT (it doesn't need llvm anymore and
we are letting it be handled automatically by upstream cmake per-architecture
conditionals).
Drop -fno-strict-aliasing build flags forcing - upstream build system is
supposed to take care of it these days. As I confirmed I still get it in the
compiler calls, this change does not necessitate a revbump either (the rest
are --changed-use territory).
Closes: https://bugs.gentoo.org/704538
Package-Manager: Portage-2.3.79, Repoman-2.3.12
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
Diffstat (limited to 'dev-util/kdbg/Manifest')
0 files changed, 0 insertions, 0 deletions