Details
-
Bug
-
Resolution: Unresolved
-
P4: Low
-
None
-
6.5
-
None
Description
The qt-cmake-standalone-test script is called from a shadow-build dir already, e.g.:
❯ pwd /Users/torarne/build/qt/6.x/tests/dialogs
❯ ../../qtbase/bin/qt-cmake-standalone-test ~/dev/qt/6.4/qtbase/tests/auto/widgets/dialogs/
So there's no need to add an extra build dir.
And we're filling the PWD with build related files as well, so it's not consistent:
❯ ls CMakeCache.txt CTestTestfile.cmake Testing build_dir compile_commands.json CMakeFiles DartConfiguration.tcl build.ninja cmake_install.cmake
This is also not what would happen with an equivialent qmake invocation, or a plain cmake invocation.
And the behavior of the Xcode generator compared to the ninja generator in this scenario is also not consistent.
It would be preferable if the qt-cmake-standalone-test helper behaved similar to the other ways you would shadow-build.
Attachments
Issue Links
- relates to
-
QTBUG-110241 "/6.5.0/Src/qtbase/tests/manual/permissions/CMakeLists.txt:4: error: Unknown CMake command "qt_internal_add_test"." while trying to configure test "qtbase/tests/manual/permissions"
- Closed
-
QTBUG-93020 Make each Qt CMake test a standalone project so that the project can be built by IDEs
- Open