-
Suggestion
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
Using BUILD_QDS_COMPONENTS requires build artifacts with extremely long paths. Sometimes, building a project might produce a cryptic error message like this (particularly on Windows):
D:\Development\QtSupport\00483290\build-TestProject-Desktop_Qt_6_5_1_MSVC2019_64bit-Debug\_deps\ds-build\src\imports\tools\eventsimulator\QuickStudioEventSimulatorplugin_QtQuick_Studio_EventSimulatorPlugin.cpp : fatal error C1083: Cannot open compiler generated file: '': Invalid argument ninja: build stopped: subcommand failed.
The reason for failure is revealed under Qt Creator's "General Messages" pane, but this is buried under a lengthy log and is not obvious to the user:
CMake Warning in D:/Development/QtSupport/00483290/build-TestProject-Desktop_Qt_6_5_1_MSVC2019_64bit-Debug/_deps/ds-src/src/imports/tools/eventsimulator/CMakeLists.txt:
The object file directory
D:/Development/QtSupport/00483290/build-TestProject-Desktop_Qt_6_5_1_MSVC2019_64bit-Debug/_deps/ds-build/src/imports/tools/eventsimulator/CMakeFiles/QuickStudioEventSimulator_qmlcache.dir/./
has 190 characters. The maximum full path to an object file is 250
characters (see CMAKE_OBJECT_PATH_MAX). Object file
.rcc/qmlcache/QuickStudioEventSimulator_qmlcache_loader.cpp.obj
cannot be safely placed under this directory. The build may not work
correctly.
It would be helpful to provide more obvious guidance to the user here, or shorten the paths used by BUILD_QDS_COMPONENTS somehow.
Unfortunately, enabling Windows 10's Long Paths feature (https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#enable-long-paths-in-windows-10-version-1607-and-later ) and CMAKE_OBJECT_PATH_MAX has no effect.
- is replaced by
-
-
- Reported
-