dev-qt/qtwebengine: refactor qt6 ebuild, various fixes incl. musl

Essentially a rewrite, so only have a not exhaustive summary
of changes rather than split commits.

Bugs addressed:
* respect *FLAGS wrt bug #652172 (fwics should be no issues left)
* hopefully fixed musl/libcxx (tested with llvm-musl) wrt bug #876520
(not planning to review Qt5's myself, so no changes on that end)

IUSE changes:
* enable alsa by default, finding that you have no audio options
  only after building is not great and alsa is cheap
* enable widgets by default, needed by both falkon and qutebrowser
* add custom-cflags, if going to use *FLAGS then should strip-flags
  like chromium's ebuild
* add opengl, unfortunately littered in QT_CONFIG(opengl) and need
  qtbase[opengl=] to avoid ABI/automagic issues
* add vulkan, has its own feature so should only need qtbase[vulkan?]
* add qml similarly to other packages

Misc:
* support EXTRA_GN like qtwebengine:5 and chromium (Gentoo-specific)
* build dir went from >9GB to ~6.3GB by dropping -g1
* drop estack+extglob, setting extglob is technically not needed for
  use in bash [[ ]] tests which is-flagq does
* drop INCLUDEPATH, tried to sed qmake files but this is using cmake
* respect NINJA env var to allow samu (NINJA_PATH was a no-op)
* use get_NINJAOPTS for NINJAFLAGS and ignore environment (NINJAOPTS
  is the var to set for this, while NINJAFLAGS is a private
  qtwebengine var, ninja does not actually use this directly)
* drop icu's bundling check for simplicity (and consistency with other
  system libraries), bug #630834 prompted adding this but does not
  seem so fragile anymore (plus iwdevtools would report lib misuse,
  albeit not headers)
* switch to bundled re2 to be spared headaches (see github PR#32281)
* optfeature on chrome-binary-plugins for widevine support
* cleanup/reduce QT_FEATURE and old comments
* fix designer automagic
* various dependencies adjustments, wrt re2c that is only needed if
  we build ninja
* do not redefine _FORTIFY_SOURCE (use gentoo's defaults), upstream
  actually switched to =3 in chromium-118 (albeit only for ChromeOS)
  and "hopefully" is fine for this older version (tests pass at least)

Also moved patches to a tarball (like qt5). It is simple small patches
mostly adjusting macros rather than add actual code, but was beginning
to add up.

Considered reducing RAM requirements a little bit (generally *seems*
not so bad), but there is rather bad spikes and I do not think it can
be considered safe unless we assume everyone is not using RAM for
anything else. Plus usage will likely keep growing with versions.

Bug: https://bugs.gentoo.org/652172
Bug: https://bugs.gentoo.org/876520
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>

0 files changed, 0 insertions, 0 deletions