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:
@@ -56,11 +56,6 @@ RunControl *AndroidAnalyzeSupport::createAnalyzeRunControl(AndroidRunConfigurati
|
||||
{
|
||||
Target *target = runConfig->target();
|
||||
AnalyzerStartParameters params;
|
||||
params.runMode = runMode;
|
||||
params.displayName = AndroidManager::packageName(target);
|
||||
params.sysroot = SysRootKitInformation::sysRoot(target->kit()).toString();
|
||||
// TODO: Not sure if these are the right paths.
|
||||
params.workingDirectory = target->project()->projectDirectory().toString();
|
||||
if (runMode == ProjectExplorer::Constants::QML_PROFILER_RUN_MODE) {
|
||||
QTcpServer server;
|
||||
QTC_ASSERT(server.listen(QHostAddress::LocalHost)
|
||||
@@ -68,8 +63,11 @@ RunControl *AndroidAnalyzeSupport::createAnalyzeRunControl(AndroidRunConfigurati
|
||||
params.analyzerHost = server.serverAddress().toString();
|
||||
}
|
||||
|
||||
AnalyzerRunControl *analyzerRunControl = AnalyzerManager::createRunControl(params, runConfig);
|
||||
(void) new AndroidAnalyzeSupport(runConfig, analyzerRunControl);
|
||||
AnalyzerRunControl *analyzerRunControl = AnalyzerManager::createRunControl(params, runConfig, runMode);
|
||||
if (analyzerRunControl) {
|
||||
analyzerRunControl->setDisplayName(AndroidManager::packageName(target));
|
||||
(void) new AndroidAnalyzeSupport(runConfig, analyzerRunControl);
|
||||
}
|
||||
return analyzerRunControl;
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user