Starting with Qt 6.10, we cross-compile all tools when building Qt for Windows on Arm. See 9254959ace4594528d9410570f4430e88763024e in qt5.git. This means that the generated qtpaths.bat script which calls the x86_64 host binary is now named host-qtpaths.bat, to allow for the existence of the arm64 qtpaths.exe executable. This breaks the cmake deployment API, which expects the script to be called qtpaths.bat when cross-compiling on Windows. At install time one sees the following warning: CMake Warning at Qt6Core/Qt6CoreDeploySupport.cmake:777 (message): No qtpaths executable found for target Qt at: . Libraries may not be deployed correctly. Extend the logic to search for both qtpaths.bat and host-qtpaths.bat. Change the existing debug message to a warning, when the qtpaths script is not found, with the ability to opt out of the warning. List the searched candidates when the warning is shown. Adapts to 9254959ace4594528d9410570f4430e88763024e in qt5.git. Amends bcdc9d7059b6ecd4e0bfb44cf5a42d87c49e3edc Amends 571201603acc731330c9af42a3aca9cda41d38fd Pick-to: 6.8 6.10 Fixes: QTBUG-142126 Change-Id: I5ddf39e5f38b53eccf4fcbbdbf1601b7e20c5934 Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>