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

ProjectExplorer: Return BuildTargetInfo from availableBuildTarget()

Browse Source 
... including build target name and display names instead of
returning QString build target names and producing display names
via displayNameForBuildTarget()

This is a mechanical intermediate step on the road to use
Target::applicationTargets().list uniformly as source of build
targets.

Change-Id: I7b0b1fb398d5061b0cec0b86890f9eaf0bb53a19
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
hjk
2018-01-03 16:41:40 +01:00
parent 94086e53bd
commit c3d87e81c5
21 changed files with 117 additions and 110 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/plugins/pythoneditor/pythoneditorplugin.cpp
View File

@@ -264,12 +264,15 @@ public:
addSupportedProjectType(PythonProjectId);
}
QList<QString> availableBuildTargets(Target *parent, CreationMode mode) const override
QList<BuildTargetInfo> availableBuildTargets(Target *parent, CreationMode mode) const override
{
Q_UNUSED(mode);
//return { Core::Id(PythonExecutableId) };
PythonProject *project = static_cast<PythonProject *>(parent->project());
return Utils::transform(project->files(ProjectExplorer::Project::AllFiles), &Utils::FileName::toString);
return Utils::transform(parent->project()->files(Project::AllFiles), [](const FileName &fn) {
BuildTargetInfo bti;
bti.targetName = fn.toString();
bti.displayName = fn.toString();
return bti;
});
}
bool canCreateHelper(Target *parent, const QString &buildTarget) const override