Alexey Edelev d4eda5d34d Make sure that tests use the module build directory but not install path ... If we configure module that is already installed it's expected that tests use the build directory to resolve all the depdencies, but not the install directory. This is especially sensetive if the module cmake scripts were changed. This changes the order of find_<package|dependency> PATHS that are used to locate Qt package. QT_EXAMPLES_CMAKE_PREFIX_PATH now is used at first, so we guarantee that we look into the build directory at first place. This trick only works if build directory is added to CMAKE_FIND_ROOT_PATH. The reason for that is the internal CMake logic that tries to relocate the search PATHs and put the paths that are subdirs of or exact CMAKE_FIND_ROOT_PATH higher in search list. Fixes: QTBUG-115730 Change-Id: Icab721f0a6eac7301c626350ab214cc4545b368b Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>		2023-09-01 11:12:23 +00:00
..
QtStandaloneTestTemplateProject	CMake: Don't set QT_BUILDING_QT for single standalone tests	2023-07-12 18:38:31 +00:00
QtBuildInternalsConfig.cmake	Make sure that tests use the module build directory but not install path	2023-09-01 11:12:23 +00:00