Profile introduction

Introduce Profiles to store sets of values that describe a system/device.

These profiles are held by a target, getting rid of much of the information
stored in the Build-/Run-/DeployConfigurations, greatly simplifying those.

This is a squash of the wip/profile branch which has been on gerrit for a
while, rebased to current master.

Change-Id: I25956c8dd4d1962b2134bfaa8a8076ae3909460f
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
This commit is contained in:
Tobias Hunger
2012-04-24 15:49:09 +02:00
parent 8c77b8c9d7
commit 2431456216
379 changed files with 12690 additions and 14437 deletions

View File

@@ -39,13 +39,8 @@
#include <QDeclarativeEngine>
namespace QmlJS {
class ModelManagerInterface;
}
namespace Utils {
class FileSystemWatcher;
}
namespace QmlJS { class ModelManagerInterface; }
namespace Utils { class FileSystemWatcher; }
namespace QmlProjectManager {
@@ -54,7 +49,6 @@ class QmlProjectItem;
namespace Internal {
class Manager;
class QmlProjectFile;
class QmlProjectTarget;
class QmlProjectNode;
} // namespace Internal
@@ -72,7 +66,8 @@ public:
Core::Id id() const;
Core::IDocument *document() const;
ProjectExplorer::IProjectManager *projectManager() const;
Internal::QmlProjectTarget *activeTarget() const;
bool supportsProfile(ProjectExplorer::Profile *p) const;
QList<ProjectExplorer::BuildConfigWidget*> subConfigWidgets();