Known failing with USE=gtk and unity builds at the moment, and
tst_qlatin1stringmatcher started eating RAM until OOM kill.
...but still months from release so not going to worry too much
at this stage.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
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>
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>
USE=gnome choice may debatable given this does not depend on gnome,
but it does nothing ootb unless gnome is detected and is intended
to integrate better with it.
Alternatively could've done USE=adwaita or USE=gnome-integration
and enable it manually on gnome profiles but does not feel necessary.
fwiw keep a local USE description to clarify.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
QtHelp may possibly be split out of qttools in the future
which would be more convenient for us as well.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Meant to add USE=openxr using the bundled copy even if not packaged,
but it fails to find its own bundled copy. May be fixed by the time
of 6.8 release, but either way would be better off packaging it if
someone wants this.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
qtbase[gui] *could* be optional but does feel worth introducing a
USE (USE=replyhandler or something) over unless someone need this
given disabling gui is rare.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Not tested, but it was added only due to having a dubious glibc
dependency. That dependency has been removed since.
Spares having to mask USE=neard on qtconnectivity w/ musl.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Qt now autodetect+add a lot of security flags by default. Not
necessarily a bad thing (uses good defaults), but prefer to let
Gentoo's own defaults and users handle these as they see fit.
syncqt was also modified to ignore qt6-build.eclass' option
to avoid overriding users' -O* value and needs a different
option.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
There's a comment in the ebuild about using eautoreconf to support
cross-compilation, but I don't think that should have been necessary in
the first place. Or at least, it shouldn't be necessary now. Aside from
that, the remaining autotools patches (requiring eautoreconf) have been
dropped. Maybe we can do without, to speed up the build and simplify the
ebuild a bit?
Signed-off-by: Michael Orlitzky <mjo@gentoo.org>
The patch _is_ simpler, but with enough hacks, we can convince the build
system to use the right paths without patching.
Signed-off-by: Michael Orlitzky <mjo@gentoo.org>