Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
None
-
6.5.2
-
None
-
MSVC build in Jenkins
-
-
69d74afd4 (dev), 4c4d21816 (6.5.2), 14a7096bd (6.6), dd5f4570a (6.5), 45e17162b (dev), cdcead0ab (dev), 68a8fdb17 (6.5), 7aea7c915 (6.5), 004a00a46 (6.5.2), 3d806a4f6 (6.5.2), c9207ef38 (6.6), 18f8aae1f (6.6)
Description
When building Qt in a Jenkins instance, the build stops with a message box that contains the help output of qtpaths.
This resulted from QTBUG-113273 - we now call qtpaths -h when building to check whether the tool can be run.
In Jenkins, the tool somehow doesn't have a console and displays the message box (instead of the help output).
The message box is displayed due to some magic in QCommandLineParser::showHelp() - there's a function that determines whether to use message boxes or not:
// Return whether to use a message box. Use handles if a console can be obtained // or we are run with redirected handles (for example, by QProcess). static inline bool displayMessageBox() { if (GetConsoleWindow()) return false; STARTUPINFO startupInfo; startupInfo.cb = sizeof(STARTUPINFO); GetStartupInfo(&startupInfo); return !(startupInfo.dwFlags & STARTF_USESTDHANDLES); }
Attachments
Issue Links
- resulted from
-
QTBUG-113273 Detect and report the "missing DLL for host tools" situation when building Qt
-
- Closed
-