Hi @Perdrix,
I should stop using macdeployqt and windeployqt and use qt_deploy_runtime_dependencies in all cases?
If I'm reading your original post correctly, it looks like you're already using qt_deploy_runtime_dependencies() for both macOS and Windows.
You can use macdeployqt and windeployqt directly, but qt_deploy_runtime_dependencies() wraps them for you. From the docs:
... when executed on macOS or Windows, the command will use either macdeployqt or windeployqt, ...
If that's now the official position I'll go with it.
I'm not sure either is considered "the official position" - both seem to be supported, and in my mind, both are good options. Though qt_deploy_runtime_dependencies() was only added in Qt 6.3, so if you want to support older Qt's, then executing {mac,win}deployqt directly is the way to go, otherwise I'd stick with qt_deploy_runtime_dependencies() if/while it meets your needs.
Either way,
if you stick with qt_deploy_runtime_dependencies(), then try adding an ADDITIONAL_EXECUTABLES parameter; or
if you want to use {mac,win}deployqt directly, then just copy all of your executables to a staging area, and run {mac,win}deployqt on all of them.
Cheers.
