Add a toolChainType() method to the ApplicationRunConfiguration.

Best effort only though. This can make detection in the debugger which
engine should be used easier.

Task-Nr: 256161

src/plugins/cmakeprojectmanager/cmakeproject.cpp

@@ -612,6 +612,15 @@ CMakeTarget CMakeProject::targetForTitle(const QString &title)
     return CMakeTarget();
 }
 
+ProjectExplorer::ToolChain::ToolChainType CMakeProject::toolChainType() const
+{
+    if (m_toolChain)
+        return m_toolChain->type();
+    return ProjectExplorer::ToolChain::UNKNOWN;
+}
+
+// CMakeFile
+
 CMakeFile::CMakeFile(CMakeProject *parent, QString fileName)
     : Core::IFile(parent), m_project(parent), m_fileName(fileName)
 {

src/plugins/cmakeprojectmanager/cmakeproject.h

@@ -105,6 +105,7 @@ public:
     CMakeTarget targetForTitle(const QString &title);
 
     QString sourceDirectory() const;
+    ProjectExplorer::ToolChain::ToolChainType toolChainType() const;
 
 protected:
     virtual void saveSettingsImpl(ProjectExplorer::PersistentSettingsWriter &writer);

src/plugins/cmakeprojectmanager/cmakerunconfiguration.cpp

@@ -217,6 +217,12 @@ void CMakeRunConfiguration::setUserEnvironmentChanges(const QList<ProjectExplore
     }
 }
 
+ProjectExplorer::ToolChain::ToolChainType CMakeRunConfiguration::toolChainType() const
+{
+    CMakeProject *pro = static_cast<CMakeProject *>(project());
+    return pro->toolChainType();
+}
+
 // Configuration widget
 
 

src/plugins/cmakeprojectmanager/cmakerunconfiguration.h

@@ -70,6 +70,7 @@ public:
     virtual void save(ProjectExplorer::PersistentSettingsWriter &writer) const;
     virtual void restore(const ProjectExplorer::PersistentSettingsReader &reader);
     virtual QString dumperLibrary() const;
+    virtual ProjectExplorer::ToolChain::ToolChainType toolChainType() const;
 
 signals:
     void baseEnvironmentChanged();