forked from qt-creator/qt-creator
Utils: Make process results accessible through QtcProcess object
The result is fully stored in the object anyway. Using the extra SynchronousProcessResponse structure only causes copies of the data and complicates access on the user side in a lot of cases. The result bits are now also accessible individually. There's obvious room for follow-up changes on the topic, e.g. ShellCommand::runCommand's parameter list could shrink to just a SynchronousProcess parameter. Change-Id: I45aa7eb23832340be06905929280c012e1217263 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
@@ -418,10 +418,10 @@ QString PluginManager::systemInformation()
|
||||
QString result;
|
||||
CommandLine qtDiag(HostOsInfo::withExecutableSuffix(
|
||||
QLibraryInfo::location(QLibraryInfo::BinariesPath) + "/qtdiag"));
|
||||
SynchronousProcess qtdiagProc;
|
||||
const SynchronousProcessResponse response = qtdiagProc.runBlocking(qtDiag);
|
||||
if (response.result == SynchronousProcessResponse::Finished)
|
||||
result += response.allOutput() + "\n";
|
||||
SynchronousProcess qtDiagProc;
|
||||
qtDiagProc.runBlocking(qtDiag);
|
||||
if (qtDiagProc.result() == QtcProcess::Finished)
|
||||
result += qtDiagProc.allOutput() + "\n";
|
||||
result += "Plugin information:\n\n";
|
||||
auto longestSpec = std::max_element(d->pluginSpecs.cbegin(), d->pluginSpecs.cend(),
|
||||
[](const PluginSpec *left, const PluginSpec *right) {
|
||||
|
||||
Reference in New Issue
Block a user