qt6 build option enabled with qt5 libraries causes a partially borked build """ option('qt', type: 'boolean', value: true, description: 'Whether Qt support is enabled') option('qt5', type: 'boolean', value: false, description: 'Whether Qt 5 support is enabled') """ from: https://github.com/audacious-media-player/audacious/blob/master/meson_options.txt In the ebuild "--enable-qt" is being used which is for qt6. The ebuild uses this even when using qt5 causing numerous very noticeable graphical bugs. please bump the dependencies to qt6! :) dev-qt/qtbase:6[gui,widgets]
Please choose a better summary next time. Please leave assignment to bug wranglers. Please add version information, can't reproduce this problem with 4.3.1.
We don't currently build it against meson, we use autotools at the moment in the ebuild, which is one source of confusion. Anyway, indeed, --enable-qt seems to prefer Qt 6, and you need --enable-qt5 to build against Qt 5. https://github.com/audacious-media-player/audacious/blob/master/acinclude.m4#L221 The deps are currently for Qt 5. It makes sense to fix the automagic first by just passing --enable-qt5 and handle the Qt 6 porting separately.
uh, 4.3.1 doesn't know what Qt 6 is: https://github.com/audacious-media-player/audacious/blob/audacious-4.3.1/acinclude.m4#L226.
(In reply to Sam James from comment #3) > uh, 4.3.1 doesn't know what Qt 6 is: > https://github.com/audacious-media-player/audacious/blob/audacious-4.3.1/ > acinclude.m4#L226. The autotools stuff is considered life support for Windows users and upstream only supports building with Gtk on there; Qt 6 support was added here three years ago: https://github.com/audacious-media-player/audacious/blob/audacious-4.2/meson.build
Sure, we can and should move to meson. But the build as-is couldn't have a specific qt6 automagic issue AFAICT.
After thinking it over I'm going to agree with the invalid resolution then. Looking through the code I'm not sure it's even possible to accidentally link against Qt6; all deps on the Qt side are versioned by name. If there's a real build bug here I'd like to see some ldd/lddtree output from the OP showing it. The complaint about graphics being screwed up is probably legit, but that ought to be a new bug at this point.
