Where are you getting your packaging files from? Upstream has no control on the choices maintainers make for their distribution packages, but we (Team Libretro) have been building against Qt6 since June without issue. You can see the commit here; I pushed it myself. :) ► https://git.launchpad.net/~libretro/libretro/+git/RetroArch-debian/commit/control?id=a28047823ab204b3d4646b446450d98254456e2e
You're welcome to switch to the packages from either of our PPAs, all of them have been fully migrated to Qt6 since that commit and have a lot more optional features enabled than either the Debian or Ubuntu archive packages. Instructions can be found here: (I wrote these as well; if they suck please let me know.) ► https://docs.libretro.com/guides/install-gnu/#personal-package-archives-ppas If you're building from source as a matter of personal preference and not necessity, then I have the utmost respect for your principles. However, I think the best that I can offer in that scenario is to suggest that you use the packaging files that we maintain here on Launchpad for the PPA builds, rather than the ones that are in the source tarballs. I keep meaning to get the ones here synced up with the main repo, but we carry a lot of patches here that I'm adamant get upstreamed first, and in a project this big there's more hoops to jump through in getting that done than I've had time for this year. The packaging files here aren't mentioned much of anywhere, but they're hardly a secret considering it's a public Git repository, haha. I'd recommend just cloning the ones here right into a debian folder at the top of the source tree for your next package build and see if that does the trick. The shell commands would be performed from the root of the source tree and look something like this: git clone --depth=1 https://git.launchpad.net/~libretro/libretro/+git/RetroArch-debian/ debian uscan --overwrite-download debuild --build=binary --no-sign The first time through it'll probably error out with a list of missing dependency packages that you never had any idea could be needed to build RetroArch. Get those taken care of (if you're on an Ubuntu LTS release, our tight version constraints for dependencies means you might need to download one or two from https://launchpad.net/~libretro/+archive/ubuntu/tmp or our Testing/Nightly PPA, link in the docs above), say a quick prayer to the Great Architect and then fire off that debuild command once more. There might be one or two more stumbles, but if you're monkeying around with d/control and d/rules already you probably know what's what, and should be off to the races pretty quick. Sorry for taking so long to see this and respond, I've been going through the ringer all year. Thanks for caring enough to file a bug report about this. Take care, now. ** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2130234 Title: retroarch build with QT6 To manage notifications about this bug go to: https://bugs.launchpad.net/libretro/+bug/2130234/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
