Doc: Resolve qdoc link warnings

- Drop link to non-existing documentation.
- Reorder links such that the target becomes the text and vice versa.
- Use correct link target names.
- Add missing qttestlib doc project dependency to qtwidgets.

Change-Id: Iaa0ea7b22326c82271b14b17c4b78c3a25a834f1
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
(cherry picked from commit f157422c58475b3b818b0dddc31289e7105967c2)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Paul Wicking 2024-02-14 10:12:26 +01:00 committed by Qt Cherry-pick Bot
parent 7cb459ea7e
commit ea0814fb7f
6 changed files with 13 additions and 11 deletions

View File

@ -422,8 +422,9 @@
\section1 Testing the model
Correctly implementing an item model can be challenging. The class
\l QAbstractItemModelTester from the \l{Qt Test} module checks for model
consistency, like the model index creation and parent-child relationships.
\l [QtTest] QAbstractItemModelTester from the \l [QtTest]{Qt Test} module
checks for model consistency, like the model index creation and
parent-child relationships.
You can test your model by just passing a model instance to the class
constructor, for instance as part of a Qt unit test:

View File

@ -323,8 +323,9 @@
\section1 Testing the model
Correctly implementing an item model can be challenging. The class
\l QAbstractItemModelTester from the \l{Qt Test} module checks for model
consistency, like the model index creation and parent-child relationships.
\l [QtTest] QAbstractItemModelTester from the \l [QtTest] {Qt Test} module
checks for model consistency, like the model index creation and
parent-child relationships.
You can test your model by just passing a model instance to the class
constructor, for instance as part of a Qt unit test:

View File

@ -11,14 +11,14 @@
\summary {Consider the BUILD_SHARED_LIBS value when creating Qt libraries.}
This policy was introduced in Qt 6.7. The policy affects the default type of the
libraries created using \l {Qt CMake API}{CMake Commands in Qt6 Core}, like
libraries created using \l {CMake Commands in Qt6 Core}{Qt CMake API}, like
\l {qt_add_library}, \l{qt_add_plugin}, \l{qt_add_qml_module}.
If the policy is set to \c OLD, the default library type that is selected is
aligned with the Qt build type, either \c shared or \c static.
If the policy is set to \c NEW, the library type is selected according to the
\l {BUILD_SHARED_LIBS}{CMake BUILD_SHARED_LIBS Documentation} value if it's set.
\l {CMake BUILD_SHARED_LIBS Documentation}{BUILD_SHARED_LIBS} value if it's set.
If \c BUILD_SHARED_LIBS is not set, the default library type falls back to the
Qt build type.

View File

@ -2,5 +2,5 @@ This variable is defined by the script named by \l QT_DEPLOY_SUPPORT. It should
only be used as part of deployment during installation or a post-build rule.
\note This is a low-level deployment API variable, and should only be used in
advanced use-cases that are not covered by the higher-level API commands like
\l{qt_generate_app_deploy_script}.
advanced use-cases that are not covered by the higher-level API commands, like
\l{qt_generate_deploy_app_script}.

View File

@ -412,8 +412,7 @@ int QDBusAbstractInterface::timeout() const
The default is \c false.
\since 6.7
\sa QDBusMessage::setInteractiveAuthorizationAllowed(),
interactiveAuthorizationAllowed()
\sa QDBusMessage::setInteractiveAuthorizationAllowed()
*/
void QDBusAbstractInterface::setInteractiveAuthorizationAllowed(bool enable)
{

View File

@ -39,7 +39,8 @@ depends += \
qtlinguist \
qthelp \
qtopengl \
qtshadertools
qtshadertools \
qttestlib
headerdirs += ..