From 8f5c6434e81f554989557ea9643aa6f323903aba Mon Sep 17 00:00:00 2001 From: Ulf Hermann Date: Mon, 17 Feb 2025 16:07:35 +0100 Subject: [PATCH] Doc: Clarify need to qt_add_standard_project_setup early Pick-to: 6.9 6.8 Fixes: QTBUG-115050 Change-Id: If8b3aabd0072bfb2bef6dea106af06524f144990 Reviewed-by: Mitch Curtis Reviewed-by: Joerg Bornemann --- src/corelib/doc/src/cmake/qt_standard_project_setup.qdoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/corelib/doc/src/cmake/qt_standard_project_setup.qdoc b/src/corelib/doc/src/cmake/qt_standard_project_setup.qdoc index 59b33f599cc..6375c179eaa 100644 --- a/src/corelib/doc/src/cmake/qt_standard_project_setup.qdoc +++ b/src/corelib/doc/src/cmake/qt_standard_project_setup.qdoc @@ -32,7 +32,8 @@ qt_standard_project_setup( This command simplifies the task of setting up a typical Qt application. It would usually be called immediately after the first \c{find_package(Qt6)} call, normally in the top level \c{CMakeLists.txt} file and before any targets -have been defined. It does the following things: +have been defined. If you call it later, it does not apply to any targets +defined before, with possibly confusing results. It does the following things: \list \li The standard CMake variables \c{CMAKE_AUTOMOC} and \c{CMAKE_AUTOUIC}