Doc: Address qt_generate_deploy_app_script issues from API review
Pick-to: 6.7 Task-number: QTBUG-121708 Change-Id: Id0beb7c3045513e1665bd4062f7236243898b7c1 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>bb10
parent
313b7c56bd
commit
5d1ddee4cc
|
|
@ -75,8 +75,9 @@ customized way.
|
|||
For Windows desktop applications, the required runtime files for the compiler
|
||||
are also installed by default. To prevent this, specify \c{NO_COMPILER_RUNTIME}.
|
||||
|
||||
You can use \c{DEPLOY_TOOL_OPTIONS} to pass additional options to the underlying
|
||||
deployment tool.
|
||||
Since Qt 6.7, you can use \c{DEPLOY_TOOL_OPTIONS} to pass additional options to
|
||||
the underlying deployment tool. This only has an effect if the underlying
|
||||
deployment tool is either macdeployqt or windeployqt.
|
||||
|
||||
For deploying a QML application, use
|
||||
\l{qt6_generate_deploy_qml_app_script}{qt_generate_deploy_qml_app_script()}
|
||||
|
|
@ -97,5 +98,13 @@ unmodified to \l{qt6_deploy_runtime_dependencies}{qt_deploy_runtime_dependencies
|
|||
|
||||
\section1 Example
|
||||
|
||||
The following example shows how to deploy an application \c{MyApp}.
|
||||
|
||||
\include cmake-generate-deploy-app-script.qdocinc
|
||||
|
||||
The following example shows how to use the \c{DEPLOY_TOOL_OPTIONS} parameter to
|
||||
pass different options to macdeployqt and windeployqt.
|
||||
|
||||
\include cmake-generate-deploy-app-script-deploy-tool-options.qdocinc
|
||||
|
||||
*/
|
||||
|
|
|
|||
|
|
@ -0,0 +1,16 @@
|
|||
\badcode
|
||||
set(deploy_tool_options_arg "")
|
||||
if(APPLE)
|
||||
set(deploy_tool_options_arg --hardened-runtime)
|
||||
elseif(WIN32)
|
||||
set(deploy_tool_options_arg --no-compiler-runtime)
|
||||
endif()
|
||||
|
||||
qt_generate_deploy_app_script(
|
||||
TARGET MyApp
|
||||
OUTPUT_SCRIPT deploy_script
|
||||
NO_UNSUPPORTED_PLATFORM_ERROR
|
||||
DEPLOY_TOOL_OPTIONS ${deploy_tool_options_arg}
|
||||
)
|
||||
install(SCRIPT ${deploy_script})
|
||||
\endcode
|
||||
Loading…
Reference in New Issue