[qt/qt/qtdeclarative]: Summary of bulk changes made

Git repository change summary for qt/qt/qtdeclarative
Pushed by mirror-service into branch '6.12'.
Changed from 0b5a02a665951781395c41cf8045ccacb9ce31cf to 2faddafd3b47319092f7d0ef7809e5c7fcab7e1e
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit b56ff9ee676ab9456f4221b3b7081075992ffe4e by SanthoshKumar Selvaraj on 31/07/2026 at 06:27..
ohos: Rename Q_OS_OHOS macro to Q_OS_HARMONY

Qt renamed the HarmonyOS platform detection macro from Q_OS_OHOS to
Q_OS_HARMONY. Update #if/#elif guards across the tests and snippets to
use the new macro name.

Note: Q_OS_OHOS will be removed once its completely migrated to
Q_OS_HARMONY

Change-Id: I1adfe1582a677d7d6e996f53be7c27787309ce84
Reviewed-by: Liang Qi <[email protected]>
(cherry picked from commit b2c8d5481c3ad3faea5e8f8fbd08cc70aca9d8dc)
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/b56ff9ee676ab9456f4221b3b7081075992ffe4e

Git commit 92b064fe87e87dfd2ff5b68ef75b3611c1cc5adb by Qt Cherry-pick Bot (on behalf of Alexei Cazacov) on 31/07/2026 at 06:31..
Doc: Mention Qt Extension for VSCode in the docs in qtdeclarative

Task-number: QTBUG-147842
Change-Id: I0e93680e0474cf5db5a3f6997595714e6c1a1da9
Reviewed-by: Leena Miettinen <[email protected]>
(cherry picked from commit ba8440c413153a6f9754c1224b605651b7c05e65)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/92b064fe87e87dfd2ff5b68ef75b3611c1cc5adb

Git commit 64a3c94ce5a519758552e8d38f5a843db42c8abf by Qt Cherry-pick Bot (on behalf of Alexei Cazacov) on 31/07/2026 at 06:34..
Doc: Fix the filters docs to use FilterBase instead of Filter

The Filter QML type was renamed to FilterBase, but the docs were not
updated. This commit fixes that.

Change-Id: I626d12409c8f54bbc94afd0c01746b3d28cd7ec0
Reviewed-by: Ulf Hermann <[email protected]>
(cherry picked from commit bb83c9f9c449e96c770e0971c939628ac364fe2a)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/64a3c94ce5a519758552e8d38f5a843db42c8abf

Git commit 2165373b8036e2667746428bb2c05f989b35f005 by Qt Cherry-pick Bot (on behalf of Olivier De Cannière) on 31/07/2026 at 06:59..
tst_qmllint: Actually check that no messages are emitted

When passing a default constructed Result object, we ignore the result
of the linting. We want to ensure no message are emitted.

Use Result::clean()

Amends 5f3545d930d4cccc4425872ceab38d9b93d7328b

Pick-to: 6.11
Change-Id: I787833effb268ca6d19f65c6006a9e0a3961472e
Reviewed-by: Sami Shalayel <[email protected]>
Reviewed-by: Fabian Kosmale <[email protected]>
(cherry picked from commit e2925c562d605d8978816988135e220fbd3df7b1)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/2165373b8036e2667746428bb2c05f989b35f005

Git commit 2faddafd3b47319092f7d0ef7809e5c7fcab7e1e by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 31/07/2026 at 08:11..
CMake: Don't depend on a QML import scan that will never run

The build-dir qt.conf partial is now generated at build time from the
QML import scanner's output, but the scan itself is set up by an
executable finalizer, which only runs for a target created with
qt_add_executable() or finalized manually. A target created with plain
add_executable() gets neither, and so ended up with a partial whose
build rule has an input that nothing produces:

    ninja: error: '.qt/qml_imports/foo_build.cmake', needed by
    '.qt/qtconfs/foo_qt.part.conf', missing and no known rule
    to make it

Whether a scan is wanted and whether one will actually be set up are two
different questions, and only the latter says anything about depending
on its output. Split them: _qt_internal_qml_import_scan_enabled() keeps
answering the first, and still gates the finalizer, so a plain
add_executable() target that is finalized manually later on has its scan
set up as before, along with the information the install-time deployment
needs. The new _qt_internal_qml_import_scan_will_run() answers the
second, and is what the deferred qt.conf writer asks. A target that will
never be finalized falls back to generating the partial from its
declared dependencies at configure time, as it did before.

Only the prediction has to be conservative: assuming no scan for a
target that ends up having one costs a qt.conf without the QML-only
imports, never a dangling build rule.

Amends dc27fcdaf26cca3fadc92cd0c9aa5398e6b0e774.

Fixes: QTBUG-148683
Change-Id: I416c197fb88cbb158ae461df5cc5b8a8d85fe99c
Reviewed-by: Alexandru Croitor <[email protected]>
(cherry picked from commit a9e34f7d5f99d82e2c4a9cdcfa885a9751d5b3ba)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/2faddafd3b47319092f7d0ef7809e5c7fcab7e1e