forked from qt-creator/qt-creator
iOS: Don't run event loop while executing xcode-select
This fixes debugging Qt Creator with the iOS plugin enabled. For unclear reasons running the event loop while executing the process locks Qt Creator up when debugging. Since running the event loop is a dangerous hack anyhow and in this case we don't have much benefit from it, just don't do it. Change-Id: Ie147d3461823587a987d0920efdfae0839fb5b67 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io> Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
@@ -68,7 +68,7 @@ void XcodeProbe::detectDeveloperPaths()
|
|||||||
Utils::SynchronousProcess selectedXcode;
|
Utils::SynchronousProcess selectedXcode;
|
||||||
selectedXcode.setTimeoutS(5);
|
selectedXcode.setTimeoutS(5);
|
||||||
const CommandLine xcodeSelect{"/usr/bin/xcode-select", {"--print-path"}};
|
const CommandLine xcodeSelect{"/usr/bin/xcode-select", {"--print-path"}};
|
||||||
Utils::SynchronousProcessResponse response = selectedXcode.run(xcodeSelect);
|
Utils::SynchronousProcessResponse response = selectedXcode.runBlocking(xcodeSelect);
|
||||||
if (response.result != Utils::SynchronousProcessResponse::Finished)
|
if (response.result != Utils::SynchronousProcessResponse::Finished)
|
||||||
qCWarning(probeLog)
|
qCWarning(probeLog)
|
||||||
<< QString::fromLatin1("Could not detect selected Xcode using xcode-select");
|
<< QString::fromLatin1("Could not detect selected Xcode using xcode-select");
|
||||||
|
Reference in New Issue
Block a user