feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Analyzer: Split AnalyzerStartParameters

Browse Source 
... into AnalyzerRunnable and AnalyzerConnection and use the
RunControl's storage instead of an own copy in AnalyzerRunControl.

This is an intermediate step on the way to remove
AnalyzerStartParameters.

Change-Id: Iee7c38781b2fd6ef030dcdada1993684cbb34c74
Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
This commit is contained in:
hjk
2016-01-18 17:49:29 +01:00
parent 077079cf2a
commit dcba1b3c36
7 changed files with 44 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/plugins/analyzerbase/analyzerruncontrol.h
View File

@@ -50,6 +50,9 @@ public:
ProjectExplorer::RunConfiguration *runConfiguration,
Core::Id runMode);
AnalyzerRunControl(ProjectExplorer::RunConfiguration *runConfiguration,
Core::Id runMode);
/// Start analyzation process.
virtual bool startEngine() = 0;
/// Trigger async stop of the analyzation process.
@@ -60,8 +63,8 @@ public:
virtual void pause() {}
virtual void unpause() {}
/// The start parameters for this engine.
const AnalyzerStartParameters &startParameters() const { return m_sp; }
const AnalyzerRunnable &runnable() const;
const AnalyzerConnection &connection() const;
virtual void notifyRemoteSetupDone(quint16) {}
virtual void notifyRemoteFinished() {}
@@ -96,7 +99,6 @@ protected:
private:
QString m_displayName; // Default to runConfig->displayName, unless overridden by setDisplayName
QString m_workingDirectory;
AnalyzerStartParameters m_sp;
};
} // namespace Analyzer