forked from qt-creator/qt-creator
Analyzer: Slim down AnalyzerStartParameters
* SysRoot can always be determined from kit. * Pass around RunMode as extra parameter not as part of AnalyzerStartParameters. That's closer to the pattern used elsewhere. * Environment was always initialized from the runconfig's EnvironmentAspect. The tools can do that directly. * Provide setter for display name for cases where it is not equal to RunConfiguration::displayName Change-Id: I811a0d7cdeb55cc37a16a593b3942abb567a2150 Reviewed-by: BogDan Vatra <bogdan@kdab.com> Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>
This commit is contained in:
@@ -80,8 +80,6 @@ RunControl *IosAnalyzeSupport::createAnalyzeRunControl(IosRunConfiguration *runC
|
||||
if (device.isNull())
|
||||
return 0;
|
||||
AnalyzerStartParameters params;
|
||||
params.runMode = ProjectExplorer::Constants::QML_PROFILER_RUN_MODE;
|
||||
params.sysroot = SysRootKitInformation::sysRoot(target->kit()).toString();
|
||||
params.debuggee = runConfig->localExecutable().toUserOutput();
|
||||
params.debuggeeArgs = Utils::QtcProcess::joinArgs(runConfig->commandLineArguments());
|
||||
params.analyzerHost = QLatin1String("localhost");
|
||||
@@ -90,9 +88,10 @@ RunControl *IosAnalyzeSupport::createAnalyzeRunControl(IosRunConfiguration *runC
|
||||
if (iosDevice.isNull())
|
||||
return 0;
|
||||
}
|
||||
params.displayName = runConfig->applicationName();
|
||||
|
||||
AnalyzerRunControl *analyzerRunControl = AnalyzerManager::createRunControl(params, runConfig);
|
||||
AnalyzerRunControl *analyzerRunControl =
|
||||
AnalyzerManager::createRunControl(params, runConfig, ProjectExplorer::Constants::QML_PROFILER_RUN_MODE);
|
||||
if (analyzerRunControl)
|
||||
analyzerRunControl->setDisplayName(runConfig->applicationName());
|
||||
(void) new IosAnalyzeSupport(runConfig, analyzerRunControl, false, true);
|
||||
return analyzerRunControl;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user