Windows Qt6 builds based on vcpkg

[m-kuhn]

Description

Refs qgis/QGIS-Enhancement-Proposals#292

This adds windows builds with Qt6, based on vcpkg dependencies.

The features WITH_BINDINGS, WITH_3D and WITH_GUI are supported and appropriately enable or disable building the required dependencies. Feature dependencies for server, opencl and quick are prepared but not yet wired.

Python support is consumed from https://github.com/open-vcpkg/python-registry/ . This is currently focused on shipping python dependencies that contain native code (dll's). Other dependencies can be installed using pip.

It is currently based on Qt 6.7.0.

Various Qt6 compatibility patches have been ported from #56980 and #56841 (QGIS code is now wchar / unicode aware for Qt6, external dependencies are patched to make them build).

TODO:

• Create an SDK to make local development easier
• Expand the developer documentation to make it easy to get started with local windows development
• Unvendor at least one "external" dependency into an overlay port, this will reduce build time and make it clear which version of external dependencies we want and what patches we added on top.
• Install psycopg2 (and other python dependencies that should be shipped)
• Check why some exes are installed in top level instead of bin

More ideas:

• Eventually use X_VCPKG_APPLOCAL_DEPS_INSTALL instead of blindly copying all .dll's, probably in a followup PR

[nyalldawson]

Nice work @m-kuhn !

Could you adapt the logic from https://github.com/qgis/QGIS/blob/master/.github/workflows/mingw64.yml#L97 to tag the artifact with the corresponding pr number and sha, and then update https://github.com/qgis/QGIS/blob/master/.github/workflows/build_artifact_comment.yml#L5 so that we get a PR comment with a direct link to download the qt6 artifacts?

[github-actions]

🪟 Windows builds ready!

Windows builds of this PR are available for testing here. Debug symbols for this build are available here.

(Built from commit 9332fba)

[troopa81]

Great work!

It looks good! (Though I'm not a Vcpkg expert)

[Guts]

After discussing it in Grenoble, it's really great to see all this work come to maturity and take the form of a PR!

[m-kuhn]

Could you adapt the logic from https://github.com/qgis/QGIS/blob/master/.github/workflows/mingw64.yml#L97 to tag the artifact with the corresponding pr number and sha, and then update https://github.com/qgis/QGIS/blob/master/.github/workflows/build_artifact_comment.yml#L5 so that we get a PR comment with a direct link to download the qt6 artifacts?

I tried but it doesn't seem to be triggered. Is it possible that this only runs once it's in master? Do you have any recommendation on developing such an action script and testing changes efficiently?

[nyalldawson]

@m-kuhn

The changes to the build artifact comment workflows must be applied in master before it'll work on a pull request.

I'd say do what everyone has to do in this situation and just directly modify the workflow on master 😂

[m-kuhn]

I'd say do what everyone has to do in this situation and just directly modify the workflow on master 😂

😱 I have close to 0 confidence in my js skills, so I'll have to do multiple commits to debug 😱

[nyalldawson]

@m-kuhn

so I'll have to do multiple commits to debug 😱

[rouault]

I'd say do what everyone has to do in this situation and just directly modify the workflow on master 😂

or push your branch to your own fork but as the master branch ?

[jef-n]

or push your branch to your own fork but as the master branch ?

That only helps half way jef-n#19 - the second workflow is not required then.