Autobuild: Use Qt6 for Windows 64bit

[hoffie]

Short description of changes

This PR switches the Autobuilds (and therefore: the releases!) to use Qt 6 for Windows 64bit builds.
The PR depends on the already merged PRs #2299 (initial Qt6 code compatibility) and #2328 (build logic Qt6 compatibility)
It only contains three small additional commits:

• Autobuild: Windows: Build with Qt 6.4.3 on 64bit
  32bit builds remain on 5.15.2, as Qt6 is not available there.

Code-wise this is the smaller change. Change-wise it is the more relevant, more invasive one.

Context: Fixes an issue?

See #2299

Does this change need documentation? What needs to be documented and how?

CHANGELOG: Build: Windows 64bit releases use Qt 6.4.3 now. Jamulus will from now on only support Windows 10 and above.

Status of this Pull Request

Ready for testing

What is missing until this pull request can be merged?

• Wait for merge of Code: Add Qt6 compatibility #2299 (Build would fail otherwise)
• Wait for merge of Build logic: Add Qt6 compatibility #2328 (Merge will conflict otherwise)
• Testing of all officially supported and affected release artifacts on relevant platforms (via beta/rc)
  • Windows 10
  • Windows 11
  • Mac
• Check if Qt6 drops support for any older platform versions (docs: Qt5, Qt6)
  • Qt6 no longer officially supports Windows 7 and 8.1 (see comments)
  • Qt6 no longer supports macOS versions on or before 10.13. I guess that's OK because we still have the legacy build for those users? (@softins: "So if we build with Qt6, High Sierra users on 10.13 would need to start using the legacy build.")

I'm hoping to merge this for 3.9.0, but if any critical issues are found or if there's too little testing, we should postpone it.

Checklist

• I've verified that this Pull Request follows the general code principles
• I tested my code and it does what I want
• My code follows the style guide
• I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
• I've filled all the content above

[hoffie]

I've rebased this PR on current master. As #2299 has been merged, the build of this PR now succeeds as well.
I've also updated it to use the latest Qt6 (6.3.0).
I've also hidden all the outdated comments regarding PR branch points.
I've also updated it to switch iOS as well.

[ann0see]

Good to know. I just wanted to add that Qt6.3.0 worked fine on my rehearsal yesterday without UI glitches.

[ann0see]

Installing the signed ipa on my phone works, but the app crashes. Hopefully it's not related to the Qt 6 move

[hoffie]

Any chance to cross-check a recent Qt5-based build?
Also, some kind of debug log would be helpful of course :)

[pljones]

Does it just need conflicts resolved and review?

[ann0see]

In theory yes. If we decide to drop Win 7 and 8.1 it's just a small test and a click on merge away.

[ann0see]

Ok. If we merge this, we need to add an auto update like on macOS. EDIT: I think we already have that.

[ann0see]

https://github.com/jamulussoftware/jamulus/actions/runs/4813082936/jobs/8569162877?pr=2300#step:10:415 Failed...

Outdated

Outdated

[pljones]

OK, my new Win 11 PC will need to have Qt6 on, then, for development. Once I get that far with the (re-)installs...

[ann0see]

I believe that the scripts need to be updated with better logic to detect the difference between QT 5 and QT 6.5. Probably the regular expressions are not exact enough like in the macOS case. I still think - after testing - we can merge this.

[ann0see]

Ok. Windows 11 Still seems to work. I'm currently downloading a Win 10 VM to try it there too.

[ann0see]

Ok. The Windows 10 VM seems ok too. I'll squash the two commits, merge it and then edit the CONTRIBUTING file.

[ann0see]

Dropping needs documentation as this will be part of the ChangeLog and is documented.