2012-10-02 09:12:39 +02:00
|
|
|
/****************************************************************************
|
2008-12-04 13:06:02 +01:00
|
|
|
**
|
2016-01-15 14:57:40 +01:00
|
|
|
** Copyright (C) 2016 The Qt Company Ltd.
|
|
|
|
|
** Contact: https://www.qt.io/licensing/
|
2008-12-04 13:06:02 +01:00
|
|
|
**
|
2012-10-02 09:12:39 +02:00
|
|
|
** This file is part of Qt Creator.
|
2008-12-04 13:06:02 +01:00
|
|
|
**
|
2012-10-02 09:12:39 +02:00
|
|
|
** Commercial License Usage
|
|
|
|
|
** Licensees holding valid commercial Qt licenses may use this file in
|
|
|
|
|
** accordance with the commercial license agreement provided with the
|
|
|
|
|
** Software or, alternatively, in accordance with the terms contained in
|
2016-01-15 14:57:40 +01:00
|
|
|
** a written agreement between you and The Qt Company. For licensing terms
|
|
|
|
|
** and conditions see https://www.qt.io/terms-conditions. For further
|
|
|
|
|
** information use the contact form at https://www.qt.io/contact-us.
|
2008-12-04 13:06:02 +01:00
|
|
|
**
|
2016-01-15 14:57:40 +01:00
|
|
|
** GNU General Public License Usage
|
|
|
|
|
** Alternatively, this file may be used under the terms of the GNU
|
|
|
|
|
** General Public License version 3 as published by the Free Software
|
|
|
|
|
** Foundation with exceptions as appearing in the file LICENSE.GPL3-EXCEPT
|
|
|
|
|
** included in the packaging of this file. Please review the following
|
|
|
|
|
** information to ensure the GNU General Public License requirements will
|
|
|
|
|
** be met: https://www.gnu.org/licenses/gpl-3.0.html.
|
2010-12-17 16:01:08 +01:00
|
|
|
**
|
2012-10-02 09:12:39 +02:00
|
|
|
****************************************************************************/
|
2008-12-04 13:06:02 +01:00
|
|
|
|
2016-01-27 10:14:00 +01:00
|
|
|
#pragma once
|
2008-12-04 13:06:02 +01:00
|
|
|
|
2009-12-09 13:54:46 +01:00
|
|
|
#include <projectexplorer/abstractprocessstep.h>
|
2008-12-04 13:06:02 +01:00
|
|
|
|
2017-03-09 23:02:32 +01:00
|
|
|
#include <QRegExp>
|
|
|
|
|
|
2009-01-13 12:37:39 +01:00
|
|
|
QT_BEGIN_NAMESPACE
|
2009-01-12 15:10:33 +01:00
|
|
|
class QLineEdit;
|
|
|
|
|
class QListWidget;
|
|
|
|
|
class QListWidgetItem;
|
2009-01-13 12:37:39 +01:00
|
|
|
QT_END_NAMESPACE
|
2009-01-12 15:10:33 +01:00
|
|
|
|
2019-05-29 18:54:45 +02:00
|
|
|
namespace Utils {
|
|
|
|
|
class CommandLine;
|
|
|
|
|
class PathChooser;
|
|
|
|
|
} // Utils
|
2014-10-02 17:51:02 +02:00
|
|
|
|
2014-02-11 21:55:42 +02:00
|
|
|
namespace ProjectExplorer { class ToolChain; }
|
2012-10-02 17:46:12 +02:00
|
|
|
|
2008-12-04 13:06:02 +01:00
|
|
|
namespace CMakeProjectManager {
|
|
|
|
|
namespace Internal {
|
|
|
|
|
|
2009-11-26 14:43:27 +01:00
|
|
|
class CMakeBuildConfiguration;
|
2015-11-26 19:50:39 +01:00
|
|
|
class CMakeRunConfiguration;
|
2016-01-07 12:33:52 +01:00
|
|
|
class CMakeBuildStepFactory;
|
2008-12-04 13:06:02 +01:00
|
|
|
|
2016-01-07 12:33:52 +01:00
|
|
|
class CMakeBuildStep : public ProjectExplorer::AbstractProcessStep
|
2008-12-04 13:06:02 +01:00
|
|
|
{
|
2009-01-12 15:10:33 +01:00
|
|
|
Q_OBJECT
|
2016-01-07 12:33:52 +01:00
|
|
|
friend class CMakeBuildStepFactory;
|
2010-01-14 17:41:29 +01:00
|
|
|
|
2008-12-04 13:06:02 +01:00
|
|
|
public:
|
2016-01-07 12:33:52 +01:00
|
|
|
explicit CMakeBuildStep(ProjectExplorer::BuildStepList *bsl);
|
2009-11-26 14:43:27 +01:00
|
|
|
|
|
|
|
|
CMakeBuildConfiguration *cmakeBuildConfiguration() const;
|
|
|
|
|
|
2016-03-30 13:06:21 +02:00
|
|
|
QString buildTarget() const;
|
2010-02-02 12:01:11 +01:00
|
|
|
bool buildsBuildTarget(const QString &target) const;
|
2016-03-30 13:06:21 +02:00
|
|
|
void setBuildTarget(const QString &target);
|
2011-10-21 23:17:58 +02:00
|
|
|
void clearBuildTargets();
|
|
|
|
|
|
2016-01-07 13:15:29 +01:00
|
|
|
QString toolArguments() const;
|
|
|
|
|
void setToolArguments(const QString &list);
|
|
|
|
|
|
2019-05-29 18:54:45 +02:00
|
|
|
Utils::CommandLine cmakeCommand(CMakeRunConfiguration *rc) const;
|
2012-10-02 17:46:12 +02:00
|
|
|
|
2015-11-13 11:06:27 +01:00
|
|
|
QVariantMap toMap() const override;
|
2010-01-14 17:41:29 +01:00
|
|
|
|
2016-01-07 12:09:59 +01:00
|
|
|
static QString cleanTarget();
|
2016-03-30 13:06:21 +02:00
|
|
|
static QString allTarget();
|
2017-04-26 15:27:01 +02:00
|
|
|
static QString installTarget();
|
2017-06-02 09:11:39 +02:00
|
|
|
static QString testTarget();
|
2017-04-26 15:27:01 +02:00
|
|
|
static QStringList specialTargets();
|
2016-01-07 12:09:59 +01:00
|
|
|
|
2012-10-02 17:46:12 +02:00
|
|
|
signals:
|
2016-01-07 13:15:29 +01:00
|
|
|
void cmakeCommandChanged();
|
2016-03-30 13:06:21 +02:00
|
|
|
void targetToBuildChanged();
|
2016-02-24 18:00:24 +01:00
|
|
|
void buildTargetsChanged();
|
2011-10-21 23:17:58 +02:00
|
|
|
|
2009-02-16 13:12:12 +01:00
|
|
|
protected:
|
2015-11-13 11:06:27 +01:00
|
|
|
void processStarted() override;
|
|
|
|
|
void processFinished(int exitCode, QProcess::ExitStatus status) override;
|
2013-02-18 11:14:41 +01:00
|
|
|
|
2015-11-13 11:06:27 +01:00
|
|
|
bool fromMap(const QVariantMap &map) override;
|
2010-01-14 17:41:29 +01:00
|
|
|
|
2009-05-05 14:56:59 +02:00
|
|
|
// For parsing [ 76%]
|
2016-01-07 15:22:53 +01:00
|
|
|
void stdOutput(const QString &line) override;
|
2010-01-14 17:41:29 +01:00
|
|
|
|
2008-12-04 13:06:02 +01:00
|
|
|
private:
|
2016-02-24 18:00:24 +01:00
|
|
|
void ctor(ProjectExplorer::BuildStepList *bsl);
|
2016-01-07 15:22:53 +01:00
|
|
|
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
bool init() override;
|
|
|
|
|
void doRun() override;
|
|
|
|
|
ProjectExplorer::BuildStepConfigWidget *createConfigWidget() override;
|
|
|
|
|
|
|
|
|
|
void runImpl();
|
|
|
|
|
void handleProjectWasParsed(bool success);
|
2016-02-25 14:18:05 +01:00
|
|
|
|
2019-01-23 22:41:58 -08:00
|
|
|
void handleBuildTargetChanges(bool success);
|
2015-11-26 19:50:39 +01:00
|
|
|
CMakeRunConfiguration *targetsActiveRunConfiguration() const;
|
2010-01-14 17:41:29 +01:00
|
|
|
|
2016-02-25 14:18:05 +01:00
|
|
|
QMetaObject::Connection m_runTrigger;
|
|
|
|
|
|
2009-04-07 13:52:28 +02:00
|
|
|
QRegExp m_percentProgress;
|
2012-10-02 17:46:12 +02:00
|
|
|
QRegExp m_ninjaProgress;
|
|
|
|
|
QString m_ninjaProgressString;
|
2016-03-30 13:06:21 +02:00
|
|
|
QString m_buildTarget;
|
2016-01-07 13:15:29 +01:00
|
|
|
QString m_toolArguments;
|
2016-01-07 15:22:53 +01:00
|
|
|
bool m_useNinja = false;
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
bool m_waiting = false;
|
2008-12-04 13:06:02 +01:00
|
|
|
};
|
|
|
|
|
|
2016-01-07 12:33:52 +01:00
|
|
|
class CMakeBuildStepConfigWidget : public ProjectExplorer::BuildStepConfigWidget
|
2008-12-04 13:06:02 +01:00
|
|
|
{
|
2009-01-12 15:10:33 +01:00
|
|
|
Q_OBJECT
|
2008-12-04 13:06:02 +01:00
|
|
|
public:
|
2016-01-07 12:33:52 +01:00
|
|
|
CMakeBuildStepConfigWidget(CMakeBuildStep *buildStep);
|
2014-09-15 11:17:31 +04:00
|
|
|
|
|
|
|
|
private:
|
2009-01-12 15:10:33 +01:00
|
|
|
void itemChanged(QListWidgetItem*);
|
2016-01-07 13:15:29 +01:00
|
|
|
void toolArgumentsEdited();
|
2009-08-06 17:26:38 +02:00
|
|
|
void updateDetails();
|
2010-02-02 12:01:11 +01:00
|
|
|
void buildTargetsChanged();
|
2013-08-26 16:01:24 +02:00
|
|
|
void selectedBuildTargetsChanged();
|
|
|
|
|
|
2016-01-07 12:33:52 +01:00
|
|
|
CMakeBuildStep *m_buildStep;
|
2016-01-07 13:15:29 +01:00
|
|
|
QLineEdit *m_toolArguments;
|
2016-01-07 15:22:53 +01:00
|
|
|
QListWidget *m_buildTargetsList;
|
2008-12-04 13:06:02 +01:00
|
|
|
};
|
|
|
|
|
|
ProjectExplorer/all: Re-organize BuildSteps/{Deploy,Build}Config setup
This follow the rough pattern of recent *RunConfigurationFactory changes
for build and deploy configurations.
- Collapse the two lines of constructors similar to what
890c1906e6fb2ec did for RunConfigurations
* Deploy* was purely mechanical
* Build* ctors are split in connects() in the ctor body
to create "empty shell for clone" etc
and build step additions in initialize() functions which
are only used in the create() case.
-- Allows to collapse the shared 'ctor()' functions, too.
- Move FooBuildConfigurationFactory::create() implementations
to FooBuildConfiguration() constructor. That was a strange
and unneeded ping-pong between factories and objects, and
furthermore allows one level less of indirection (and for a
later, left out here, some reduction of the
FooBuildConfiguration interfaces that were only used to
accommodate the *Factory::create() functions.
- Most {Build,Deploy}Configuration{,Factory} classes had a canHandle(),
but there wasn't one in the base classses. Have one there.
- Most canHandle() functions were checking simple restrictions on
e.g. project or target types, specify those by setters in the
constructors instead and check them in the base canHandle()
- clone() is generally replaced by a creation of a "shell object"
and a fromMap(source->toMap()), implemented in the base, there
are two cases left for Android and Qbs that needed(?) some extra
polish
- generally use canHandle() in base implementation, instead
of doing that in all Derived::canFoo()
- as a result, canCreate/create/canClone/clone reimplementations
are not needed anymore, keep the base implementation for
now (could be inlined into their only users later), but
de-virtualize them.
- Combine Ios{Preset,DSym}BuildStepFactory. There was only one
'dsym' build step they could create.
- Split the 'mangled' id into the ProjectConfiguration subtype
specific constant identifier, and a QString extraId() bit.
Only maintain the mangled id in saved settings.
- Make ProjectConfiguration::m_id a constant member, adapt
all constructors of derived classe.
Not done in this patch:
- Finish possible cosmetic changes on top
- Add a way to specify restrictions to supported Qt versions
(used in Android/Ios), as the base implementation does not
depend on the qtsupport plugin
- Combine the QList<X> availableFoo() + createFoo(X) function
pairs to somthing like a direct
QList<struct { X; std::function<X()>; }> fooCreators()
to avoid e.g. the baseId.withSuffix() <-> id.suffixAfter(base)
pingpong
- Remove the *Factories from the global object pool
- Do something about priority(). Falling back to plain
qmake in android+qmake setup is not helpful.
Change-Id: I2be7d88d554c5aa8b7db8edf5b93278e1ae0112a
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
2017-11-29 12:28:40 +01:00
|
|
|
class CMakeBuildStepFactory : public ProjectExplorer::BuildStepFactory
|
2008-12-04 13:06:02 +01:00
|
|
|
{
|
2010-01-14 17:41:29 +01:00
|
|
|
public:
|
ProjectExplorer/all: Re-organize BuildSteps/{Deploy,Build}Config setup
This follow the rough pattern of recent *RunConfigurationFactory changes
for build and deploy configurations.
- Collapse the two lines of constructors similar to what
890c1906e6fb2ec did for RunConfigurations
* Deploy* was purely mechanical
* Build* ctors are split in connects() in the ctor body
to create "empty shell for clone" etc
and build step additions in initialize() functions which
are only used in the create() case.
-- Allows to collapse the shared 'ctor()' functions, too.
- Move FooBuildConfigurationFactory::create() implementations
to FooBuildConfiguration() constructor. That was a strange
and unneeded ping-pong between factories and objects, and
furthermore allows one level less of indirection (and for a
later, left out here, some reduction of the
FooBuildConfiguration interfaces that were only used to
accommodate the *Factory::create() functions.
- Most {Build,Deploy}Configuration{,Factory} classes had a canHandle(),
but there wasn't one in the base classses. Have one there.
- Most canHandle() functions were checking simple restrictions on
e.g. project or target types, specify those by setters in the
constructors instead and check them in the base canHandle()
- clone() is generally replaced by a creation of a "shell object"
and a fromMap(source->toMap()), implemented in the base, there
are two cases left for Android and Qbs that needed(?) some extra
polish
- generally use canHandle() in base implementation, instead
of doing that in all Derived::canFoo()
- as a result, canCreate/create/canClone/clone reimplementations
are not needed anymore, keep the base implementation for
now (could be inlined into their only users later), but
de-virtualize them.
- Combine Ios{Preset,DSym}BuildStepFactory. There was only one
'dsym' build step they could create.
- Split the 'mangled' id into the ProjectConfiguration subtype
specific constant identifier, and a QString extraId() bit.
Only maintain the mangled id in saved settings.
- Make ProjectConfiguration::m_id a constant member, adapt
all constructors of derived classe.
Not done in this patch:
- Finish possible cosmetic changes on top
- Add a way to specify restrictions to supported Qt versions
(used in Android/Ios), as the base implementation does not
depend on the qtsupport plugin
- Combine the QList<X> availableFoo() + createFoo(X) function
pairs to somthing like a direct
QList<struct { X; std::function<X()>; }> fooCreators()
to avoid e.g. the baseId.withSuffix() <-> id.suffixAfter(base)
pingpong
- Remove the *Factories from the global object pool
- Do something about priority(). Falling back to plain
qmake in android+qmake setup is not helpful.
Change-Id: I2be7d88d554c5aa8b7db8edf5b93278e1ae0112a
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
2017-11-29 12:28:40 +01:00
|
|
|
CMakeBuildStepFactory();
|
2008-12-04 13:06:02 +01:00
|
|
|
};
|
|
|
|
|
|
2009-03-18 13:33:00 +01:00
|
|
|
} // namespace Internal
|
|
|
|
|
} // namespace CMakeProjectManager
|