forked from qt-creator/qt-creator
TargetSetupPage: Generalize the page
Generalize the target setup page and move it into projectexplorer Move the qmake specific code into a projectimporter class with a specialization for qmake projects in the qt4projectmanager. This change depends heavily on the BuildConfigurationFactory cleanups done earlier and completes that change in such a way that generic build configuration factories are now in theory possible. The remaining problem is how to select the best factory of several that claim to be able to handle a kit and that is left for the next patch. Change-Id: I47134cb1938c52adebcdc1ddfe8dbf26abbbbeee Reviewed-by: Daniel Teske <daniel.teske@digia.com>
This commit is contained in:
@@ -102,6 +102,23 @@ QList<BuildInfo *> GenericBuildConfigurationFactory::availableBuilds(const Targe
|
||||
return result;
|
||||
}
|
||||
|
||||
bool GenericBuildConfigurationFactory::canSetup(const Kit *k, const QString &projectPath) const
|
||||
{
|
||||
return k && Core::MimeDatabase::findByFile(QFileInfo(projectPath))
|
||||
.matchesType(QLatin1String(Constants::GENERICMIMETYPE));
|
||||
}
|
||||
|
||||
QList<BuildInfo *> GenericBuildConfigurationFactory::availableSetups(const Kit *k, const QString &projectPath) const
|
||||
{
|
||||
QList<BuildInfo *> result;
|
||||
QTC_ASSERT(canSetup(k, projectPath), return result);
|
||||
BuildInfo *info = createBuildInfo(k, Utils::FileName::fromString(ProjectExplorer::Project::projectDirectory(projectPath)));
|
||||
//: The name of the build configuration created by default for a generic project.
|
||||
info->displayName = tr("Default");
|
||||
result << info;
|
||||
return result;
|
||||
}
|
||||
|
||||
BuildConfiguration *GenericBuildConfigurationFactory::create(Target *parent, const BuildInfo *info) const
|
||||
{
|
||||
QTC_ASSERT(canCreate(parent), return 0);
|
||||
|
||||
Reference in New Issue
Block a user