4 Commits
Author SHA1 Message Date
Janek Bevendorff 09e34ba86c Ensure Qt's TLS plugins are deployed on macOS
For whatever reason, macdeployqt does not deploy the TLS plugins on its own. We need to find them manually.

Fixes #13855
2026-10-24 01:13:43 +02:00
Janek Bevendorff 84f5e58c29 Add -DWITH_BUILD_QT CMake option and --build-qt release-tool flags to build Qt6 via vcpkg instead of using binaries from the system
Also advance vcpkg baseline to pull in Qt 6.11 and to fix compilation
with macOS SDK 26.
2026-09-14 14:31:24 -04:00
luzpaz 880cc230ac Fix various typos (#8748) 2023-01-29 09:38:44 -05:00
alcroito ab153a24ec Run macdeployqt only once at install time
Instead of running macdeployqt once for each extra helper binary and
plugin (plus the main run for the application itself), collect all the
binaries that should be processed and run macdeloyqt only once after
all the binaries have been installed.

This also moves the main app macdeployqt call from a POST_BUILD step
to an install(CODE) step, making increment rebuilds of the app faster.

To ensure that macdeployqt is called after all the binaries are
installed, a new post_install subdirectory is needed to
circumvent CMake's limitation regarding the default order of
installation.
CMake first runs the current directory install() calls and then it's
child subdirectory ones. Because we want macdeployqt to be the last
install() call, it needs to be done inside a subdirectory that is
added last.

Note due to a bug in macdeployqt, the deployed app inside the .dmg
file will fail to run on arm macs, due to broken code signature.
See https://bugreports.qt.io/browse/QTBUG-101696 for details.

For the final release, the release-tool should take care of proper
resigning.
2022-03-21 00:15:57 +01:00