Valgrind: Start custom actions more directly

This does not need to go through the PE machinery.

Change-Id: If0b2fde5309d7e119e8ac27245a22939b68d847d
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
This commit is contained in:
hjk
2015-06-19 08:34:46 +02:00
parent 8a1c603c0d
commit 92ec05c9bd
7 changed files with 42 additions and 28 deletions

View File

@@ -40,6 +40,7 @@ const char CallgrindToolId[] = "Callgrind";
const char CallgrindLocalActionId[] = "Callgrind.Local";
const char CallgrindRemoteActionId[] = "Callgrind.Remote";
class ValgrindRunControl;
class CallgrindToolPrivate;
class CallgrindTool : public QObject
@@ -50,7 +51,7 @@ public:
CallgrindTool(QObject *parent);
~CallgrindTool();
Analyzer::AnalyzerRunControl *createRunControl(const Analyzer::AnalyzerStartParameters &sp,
ValgrindRunControl *createRunControl(const Analyzer::AnalyzerStartParameters &sp,
ProjectExplorer::RunConfiguration *runConfiguration = 0);
QWidget *createWidgets();