summaryrefslogtreecommitdiff
path: root/dev-qt/qtwebengine
AgeCommit message (Collapse)Author
2024-10-08dev-qt/qtwebengine: add 6.8.0Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-10-08dev-qt/qtwebengine: drop 6.8.0_rcIonen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-27dev-qt/qtwebengine: add 6.7.3Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-24dev-qt/qtwebengine: fix build with USE=-vaapi in 6.8+Ionen Wolkens
Per the comment, already couldn't use system's libvpv when USE=vaapi is enabled (this is intentionally enforced by the build system rather than "broken"), and now USE=-vaapi fails to build in 6.8 with system's. Seems like an easy fix but (even if fixed) feel it would be simpler keep the same setup regardless of USE=vaapi until vaapi allows using system's. I hardly test USE=-vaapi and missed that it broke, and I assume this holds for upstream too. qtwebengine does keep bundled libvpx either up to date or backports security fixes, albeit bumps are less frequent and fixes could lag a bit (not that we had a choice with USE=vaapi either way, unless drop vaapi support). As a small perk, it'll spare users from rebuilding qtwebengine on libvpx subslot bumps which happen now and then. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-24dev-qt/qtwebengine: add 6.8.0_rcIonen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-22dev-qt/qtwebengine: update patchsets in live (qt6)Ionen Wolkens
6.7-12 -> 6.7-13, and 6.8-3 -> 6.8-4 changes: Updated: * cstdint.patch (merged extra chunk from files/) Dropped: * clang19.patch (upstreamed) * gcc15.patch (upstreamed) Note: 6.8 patches are known to not apply right now, but that is because they are made for the 6.8.0 branch (in preparation for release) while the ebuild uses dev 6.8 which moved on to 6.8.1 and broke a patch. Will update again sometime only after release is out of the way given do not care to test 6.8.1 right now. Or earlier if the change is backported to 6.8.0 in the interim. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-12dev-qt/qtwebengine: fix build with gcc+musl+USE=-jumboIonen Wolkens
Closes: https://bugs.gentoo.org/939519 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-03dev-qt/qtwebengine: cleanup exporting NINJAIonen Wolkens
Not used anymore given patch was removed in favor of relying on app-alternatives/ninja to select. NINJAFLAGS is still recognized by a patch (not by ninja!). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-03dev-qt/qtwebengine: update build space requirement for 6.8+Ionen Wolkens
Last build test for 6.8.9999 used exactly 8.0GiB, ebuild checks for 8G but that's too borderline and should do +1 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-02dev-qt/qtwebengine: skip tst_certificateerror in 6.8+Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-09-02dev-qt/qtwebengine: update liveIonen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-08-14dev-qt/qtwebengine: update 6.7 and 6.8 patchsetsIonen Wolkens
6.7-10 -> 6.7-11, and 6.8-2 -> 6.8-3 changes: Added: * clang19.patch (imported from files/) * musl-no-settls.patch (wrt bug #937875) 6.7-10 -> 6.7-11 specific changes: Added: * QTBUG-113574.patch (imported from files/) 6.7-11 -> 6.7-12 changes (in preparation for 6.7.3): Removed: * ninja1.12.patch (upstreamed) Technically needs a revbump for bug #937875 (runtime issue), but do not wish for every users to rebuild over a musl fix. musl users reading this are invited to `emerge -1 qtwebengine:6`. Stable users are not believed to be affected, and there's to hope 6.7.3 releases & is stabilized before musl-1.2.5 is (or a := forces a rebuild first). Closes: https://bugs.gentoo.org/937875 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-08-09dev-qt/qtwebengine: fix build with clang-19Ionen Wolkens
Closes: https://bugs.gentoo.org/937541 Thanks-to: Alfred Wingate Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-07-29dev-qt/qtwebengine: fix re2 compatibilityAliaksei Urbanski
Use bundled re2 to avoid the compatibility issue for qtwebengine-5.15.14_p20240510. Closes: https://bugs.gentoo.org/913923 Bug: https://bugs.gentoo.org/936884 Signed-off-by: Aliaksei Urbanski <aliaksei.urbanski@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/37785 Signed-off-by: Sam James <sam@gentoo.org>
2024-07-28dev-qt/qtwebengine: fix build with GCC 15 (qt5)Sam James
Thanks to Ionen for finding the QUIC patch. We may end up needing more for qt5. Closes: https://bugs.gentoo.org/936416 Signed-off-by: Sam James <sam@gentoo.org>
2024-07-23dev-qt/qtwebengine: update 6.7 and 6.8 patchsetsIonen Wolkens
6.7-9 -> 6.7-10 changes: Added: * gcc15.patch (with two fixes wrt bug #936415, built fine with all USE enabled using gcc-15.0.0_pre20240721) 6.8-1 -> 6.8-2 changes: Added: * gcc15.patch (including an additional fix for 6.8+, untested) Removed: * ninja1.12.patch (upstreamed) + minor rebasing where needed Closes: https://bugs.gentoo.org/936415 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-07-15dev-qt/qtwebengine: drop 6.7.1Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-07-10dev-qt/qtwebengine: Stabilize 6.7.2 amd64, #935728Matoro Mahri
Signed-off-by: Matoro Mahri <matoro_gentoo@matoro.tk> Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-07-08dev-qt/qtwebengine: Stabilize 6.7.2 arm64, #935728Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2024-07-02dev-qt/qtwebengine: backport wayland text rendering fix (qt6)Ionen Wolkens
See patch header. Tempting to revbump, albeit will still spare users for now. Will at least give stable users the fixed vresion when stabilized soon. ~testing users annoyed by this are invited to manually rebuild. Also add to 6.7.9999 so it is not forgotten with 6.7.3, "currently" not marked to be picked to the 6.7 branch for the 6.7.3 release and may or may not still be needed until 6.8.0. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-20dev-qt/qtwebengine: alternate fix for USE="pdfium -pulseaudio" (qt6)Ionen Wolkens
Just realized the issue is self-inflicted. The pkg-config check is done only if "use_pulseaudio && link_pulseaudio" and the latter is passed by us rather than Qt. It seemed harmless to be unconditional given the main switch disabled it (which technically sounds better), but given it doesn't for pdfium let's change that and do it for pipewire as well while at it. Bug: https://bugs.gentoo.org/934635 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-20dev-qt/qtwebengine: fix build with USE="pdfium -pulseaudio" (qt6)Ionen Wolkens
Or hopefully anyway, have not tested the full build without libpulse, but it at least no longer looks for it. Unclear whether pdfium was automagically linking with it, or just looking for it for nothing while unused. The former technically needs a revbump, but not worth it given the long build times and how pdfium is scarcely used. Closes: https://bugs.gentoo.org/934635 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-18dev-qt/qtwebengine: add 6.7.2Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-11dev-qt/qtwebengine: move libglvnd[X] to dependIonen Wolkens
While it is indeed included, odds are GL/glx.h is not truly needed (included for nothing, does not link with libGLX nor seem to dlopen it), may need review if manage to make X optional in 6.8+ but is not important for now. Untested whether it includes it even with USE=-opengl like it does for some other GL headers, but leave it like that for now (USE=opengl is mostly to control qt's dependency). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-11dev-qt/qtwebengine: add libglvnd[X] as dependChristopher Bayliss
* when built on non-desktop profile systems, the qtwebengine[opengl] build fails because it needs GL/glx.h Signed-off-by: Christopher Bayliss <cjbdev@icloud.com> Closes: https://github.com/gentoo/gentoo/pull/37062 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-08dev-qt/qtwebengine: drop 6.7.0Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-08dev-qt/qtwebengine: Stabilize 6.7.1 arm64, #932347Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2024-06-06dev-qt/qtwebengine: drop 5.15.13_p20240510Andreas Sturmlechner
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2024-06-04dev-qt/qtwebengine: add 6.8.9999Ionen Wolkens
Not really tested yet beside checking that the patches apply. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-04dev-qt/qtwebengine: update 6.7 patchset in live, and add 6.8+ oneIonen Wolkens
6.7-8 -> 6.7-9 changes: Removed: * flags.patch (tentative, commit 3373a27c to qt6-build.eclass *should* make it unnecessary and gives us less to maintain -- does require re-adding symbol_level=0 Gn arg) 6.7-9 -> 6.8-1 has no changes beside rebasing with chromium-118 in preparation for adding 6.8.9999. ninja-1.12.patch will likely be upstreamed before next releases but kept for now given testing is annoying without it. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-04dev-qt/qtwebengine: add two missing libX* build-deps (qt6)Ionen Wolkens
Unlikely to be missing, but seen a build-time check for these and it would not hurt to be sure (does not link with these, have not dug further but may be optional use with dlopen. On a side-note, it may now be possible ot make X optional in 6.8+ -- not trying this is yet but will probably do before 6.8.0_rc releases (keeping the safe status quo for now). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-06-02dev-qt/qtwebengine: Stabilize 6.7.1 amd64, #932347Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2024-06-01dev-qt/qtwebengine: Stabilize 5.15.14_p20240510 arm64, #933196Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2024-06-01dev-qt/qtwebengine: Stabilize 5.15.14_p20240510 amd64, #933196Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2024-05-31dev-qt/qtwebengine: Add missing python_check_deps()Andreas Sturmlechner
Bug: https://bugs.gentoo.org/931970 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2024-05-30dev-qt/qtwebengine: Fix build w/ ICU-75Andreas Sturmlechner
Patch sourced from Arch Linux. Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2024-05-30dev-qt/qtwebengine: Add python3.12, add missing BDEPEND for catapultAndreas Sturmlechner
Bug: https://bugs.gentoo.org/925718 Bug: https://bugs.gentoo.org/931970 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2024-05-30dev-qt/qtwebengine: add 5.15.14_p20240510Andreas Sturmlechner
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2024-05-23dev-qt/qtwebengine: drop vulnerable 5.15.13_p20240322Andreas Sturmlechner
Bug: https://bugs.gentoo.org/931960 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2024-05-23dev-qt/qtwebengine: Stabilize 5.15.13_p20240510 amd64, #931961Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2024-05-22dev-qt/qtwebengine: Stabilize 5.15.13_p20240510 arm64, #931961Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2024-05-21dev-qt/qtwebengine: restore chromium-drop-catapult patch (qt5)Ionen Wolkens
Hardly tested (I don't use qt5) but it should be better than leaving as-is. Closes: https://bugs.gentoo.org/931970 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-05-20dev-qt/qtwebengine: add 6.7.1Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-05-17dev-qt/qtwebengine: update 6.7 patchset in liveIonen Wolkens
6.7-7 -> 6.7-8 changes: Removed: * clang18.patch (upstreamed) Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-05-17dev-qt/qtwebengine: update evex512 workaround for fixed llvm versionIonen Wolkens
The has_version is not *necessary* but will make it easier to know it's safe to drop when it becomes essentially a no-op. Bug: https://bugs.gentoo.org/931623 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-05-15dev-qt/qtwebengine: add 5.15.13_p20240510Andreas Sturmlechner
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2024-05-13dev-qt/qtwebengine: enable py3.13 (qt6)Ionen Wolkens
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-05-10dev-qt/qtwebengine: note reminder of when to drop workaroundIonen Wolkens
Bug: https://bugs.gentoo.org/931623 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-05-09dev-qt/qtwebengine: improve clang-18 workaround w/ -mevex512 (qt6)Ionen Wolkens
Hoping it will be a short-lived and that this will be improved/fixed in clang itself. (have not tried nor looked at qtwebengine:5) For some rough explanation from the little I get from this: clang-18 added -mevex512 (missing from 17), and then -march=native is a bit quirky in that unlike -march=exact it goes out of its way to disable it resulting in e.g. -march=skylake -mavx512f = -mevex512 is auto-enabled -march=skylake -mevex512 = not "enabled" but can be used -march=native(skylake) -mavx512f = forced off(!) And then units that use avx512 / pass -mavx512f (for use with runtime cpu detection) end in build failure without evex512. Always passing -mevex512 on a machine without avx512 "seems" safe, it does not even set __EVEX512__ and believe won't use any avx512 instructions on a whim (__EVEX512__ does get set if add -mavx512f). Or at least my skylake (not skylake-x) passes test + can use the qtwebengine built that way. Considered passing only for files that need it at first with a patch (sounded safer), but chromium's Gn files don't have a variable to test clang version that I could see (or at least not in old qtwebengine) and didn't want this to become more involved nor use conditional patching. The !avx512 check may not be super necessary, but have not dug into the implications of forcing it when avx512 is actually enabled (sounds there are cases where it needs to be off, leaving it to compiler). Bug: https://bugs.gentoo.org/931623 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
2024-05-08dev-qt/qtwebengine: "fix" build with clang-18 + -march=native (qt6)Ionen Wolkens
Needs more looking into but want a quick workaround before 6.7.1 releases with clang users having started to use 18. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>