forked from qt-creator/qt-creator
CMake: Remove clearBuildTarget from CMakeBuildStep
That method makes little sense, considering that there can only ever be one build target. Change-Id: I53d555fa7d713dd8c05b4a9f5944908afeee859f Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
@@ -321,11 +321,6 @@ void CMakeBuildStep::setBuildTarget(const QString &buildTarget)
|
|||||||
emit targetToBuildChanged();
|
emit targetToBuildChanged();
|
||||||
}
|
}
|
||||||
|
|
||||||
void CMakeBuildStep::clearBuildTargets()
|
|
||||||
{
|
|
||||||
m_buildTarget.clear();
|
|
||||||
}
|
|
||||||
|
|
||||||
QString CMakeBuildStep::toolArguments() const
|
QString CMakeBuildStep::toolArguments() const
|
||||||
{
|
{
|
||||||
return m_toolArguments;
|
return m_toolArguments;
|
||||||
|
|||||||
@@ -64,7 +64,6 @@ public:
|
|||||||
QString buildTarget() const;
|
QString buildTarget() const;
|
||||||
bool buildsBuildTarget(const QString &target) const;
|
bool buildsBuildTarget(const QString &target) const;
|
||||||
void setBuildTarget(const QString &target);
|
void setBuildTarget(const QString &target);
|
||||||
void clearBuildTargets();
|
|
||||||
|
|
||||||
QString toolArguments() const;
|
QString toolArguments() const;
|
||||||
void setToolArguments(const QString &list);
|
void setToolArguments(const QString &list);
|
||||||
|
|||||||
@@ -155,7 +155,6 @@ void BuildCMakeTargetLocatorFilter::accept(Core::LocatorFilterEntry selection,
|
|||||||
|
|
||||||
// Change the make step to build only the given target
|
// Change the make step to build only the given target
|
||||||
QString oldTarget = buildStep->buildTarget();
|
QString oldTarget = buildStep->buildTarget();
|
||||||
buildStep->clearBuildTargets();
|
|
||||||
buildStep->setBuildTarget(selection.displayName);
|
buildStep->setBuildTarget(selection.displayName);
|
||||||
|
|
||||||
// Build
|
// Build
|
||||||
|
|||||||
Reference in New Issue
Block a user