2012-10-02 09:12:39 +02:00
|
|
|
/****************************************************************************
|
2009-11-23 12:11:48 +01:00
|
|
|
**
|
2016-01-15 14:57:40 +01:00
|
|
|
** Copyright (C) 2016 The Qt Company Ltd.
|
|
|
|
|
** Contact: https://www.qt.io/licensing/
|
2009-11-23 12:11:48 +01:00
|
|
|
**
|
2012-10-02 09:12:39 +02:00
|
|
|
** This file is part of Qt Creator.
|
2009-11-23 12:11:48 +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.
|
2009-11-23 12:11:48 +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
|
|
|
****************************************************************************/
|
2009-11-23 12:11:48 +01:00
|
|
|
|
2016-01-27 10:14:00 +01:00
|
|
|
#pragma once
|
2009-11-23 12:11:48 +01:00
|
|
|
|
2016-02-03 13:52:50 +01:00
|
|
|
#include "cmakeconfigitem.h"
|
2016-10-06 11:31:27 +02:00
|
|
|
#include "cmakeproject.h"
|
2016-02-24 18:00:24 +01:00
|
|
|
#include "configmodel.h"
|
2016-02-03 13:52:50 +01:00
|
|
|
|
2017-02-06 16:59:53 +01:00
|
|
|
#include <cpptools/cpprawprojectpart.h>
|
|
|
|
|
|
2009-11-23 12:11:48 +01:00
|
|
|
#include <projectexplorer/buildconfiguration.h>
|
2018-12-20 18:51:12 +01:00
|
|
|
#include <projectexplorer/buildtargetinfo.h>
|
|
|
|
|
#include <projectexplorer/deploymentdata.h>
|
2009-11-23 12:11:48 +01:00
|
|
|
|
2009-11-23 13:29:45 +01:00
|
|
|
namespace CMakeProjectManager {
|
2019-01-29 16:51:17 +01:00
|
|
|
class CMakeExtraBuildInfo;
|
2015-03-10 14:24:14 +01:00
|
|
|
class CMakeProject;
|
2013-07-22 15:53:57 +02:00
|
|
|
|
2009-11-23 13:29:45 +01:00
|
|
|
namespace Internal {
|
|
|
|
|
|
2016-02-24 18:00:24 +01:00
|
|
|
class BuildDirManager;
|
|
|
|
|
class CMakeBuildSettingsWidget;
|
2009-11-23 13:29:45 +01:00
|
|
|
|
2009-11-23 12:11:48 +01:00
|
|
|
class CMakeBuildConfiguration : public ProjectExplorer::BuildConfiguration
|
|
|
|
|
{
|
2009-11-25 18:49:59 +01:00
|
|
|
Q_OBJECT
|
2010-01-18 12:11:04 +01:00
|
|
|
|
2019-01-29 08:55:52 +01:00
|
|
|
friend class ProjectExplorer::BuildConfigurationFactory;
|
2018-05-04 16:52:21 +02:00
|
|
|
CMakeBuildConfiguration(ProjectExplorer::Target *parent, Core::Id id);
|
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
|
|
|
|
2009-11-23 12:11:48 +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
|
|
|
void emitBuildTypeChanged();
|
2009-11-25 18:50:20 +01:00
|
|
|
|
2016-02-11 16:33:15 +01:00
|
|
|
bool isEnabled() const override;
|
2014-06-19 15:29:11 +02:00
|
|
|
|
2017-09-28 11:32:39 +02:00
|
|
|
CMakeConfig configurationForCMake() const;
|
|
|
|
|
CMakeConfig configurationFromCMake() const;
|
2015-09-10 16:17:38 +02:00
|
|
|
|
2016-02-11 16:33:15 +01:00
|
|
|
QString error() const;
|
2016-05-12 17:23:03 +02:00
|
|
|
QString warning() const;
|
2016-02-11 16:33:15 +01:00
|
|
|
|
2018-12-20 18:51:12 +01:00
|
|
|
QStringList buildTargetTitles() const;
|
|
|
|
|
ProjectExplorer::BuildTargetInfoList appTargets() const;
|
|
|
|
|
ProjectExplorer::DeploymentData deploymentData() const;
|
2016-02-24 18:00:24 +01:00
|
|
|
|
2016-03-01 14:12:35 +01:00
|
|
|
static Utils::FileName
|
|
|
|
|
shadowBuildDirectory(const Utils::FileName &projectFilePath, const ProjectExplorer::Kit *k,
|
|
|
|
|
const QString &bcName, BuildConfiguration::BuildType buildType);
|
|
|
|
|
|
2016-11-14 15:18:25 +01:00
|
|
|
// Context menu action:
|
|
|
|
|
void buildTarget(const QString &buildTarget);
|
|
|
|
|
|
2016-02-11 16:33:15 +01:00
|
|
|
signals:
|
|
|
|
|
void errorOccured(const QString &message);
|
2016-05-12 17:23:03 +02:00
|
|
|
void warningOccured(const QString &message);
|
2016-02-11 16:33:15 +01:00
|
|
|
|
2017-09-28 11:32:39 +02:00
|
|
|
void configurationForCMakeChanged();
|
|
|
|
|
|
2009-11-25 18:50:20 +01:00
|
|
|
private:
|
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
|
|
|
QVariantMap toMap() const override;
|
|
|
|
|
BuildType buildType() const override;
|
|
|
|
|
|
2019-01-29 16:51:17 +01:00
|
|
|
void initialize(const ProjectExplorer::BuildInfo &info) override;
|
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
|
|
|
QString disabledReason() const override;
|
|
|
|
|
|
|
|
|
|
ProjectExplorer::NamedWidget *createConfigWidget() override;
|
|
|
|
|
|
|
|
|
|
bool fromMap(const QVariantMap &map) override;
|
2017-04-07 11:15:26 +02:00
|
|
|
|
2017-09-28 11:32:39 +02:00
|
|
|
bool isParsing() const;
|
|
|
|
|
|
2017-10-24 15:16:26 +02:00
|
|
|
enum ForceEnabledChanged { False, True };
|
2017-04-07 11:15:26 +02:00
|
|
|
void clearError(ForceEnabledChanged fec = ForceEnabledChanged::False);
|
2017-09-28 11:32:39 +02:00
|
|
|
|
|
|
|
|
void setBuildTargets(const QList<CMakeBuildTarget> &targets);
|
|
|
|
|
void setConfigurationFromCMake(const CMakeConfig &config);
|
|
|
|
|
void setConfigurationForCMake(const QList<ConfigModel::DataItem> &items);
|
|
|
|
|
void setConfigurationForCMake(const CMakeConfig &config);
|
2016-02-24 18:00:24 +01:00
|
|
|
|
|
|
|
|
void setError(const QString &message);
|
2016-05-12 17:23:03 +02:00
|
|
|
void setWarning(const QString &message);
|
2016-02-24 18:00:24 +01:00
|
|
|
|
2017-09-28 11:32:39 +02:00
|
|
|
CMakeConfig m_configurationForCMake;
|
2016-02-11 16:33:15 +01:00
|
|
|
QString m_error;
|
2016-05-12 17:23:03 +02:00
|
|
|
QString m_warning;
|
2013-08-16 17:45:16 +02:00
|
|
|
|
2017-09-28 11:32:39 +02:00
|
|
|
CMakeConfig m_configurationFromCMake;
|
|
|
|
|
QList<CMakeBuildTarget> m_buildTargets;
|
2016-02-24 18:00:24 +01:00
|
|
|
|
|
|
|
|
friend class CMakeBuildSettingsWidget;
|
2016-04-18 13:06:41 +02:00
|
|
|
friend class CMakeProjectManager::CMakeProject;
|
2017-09-28 11:32:39 +02:00
|
|
|
friend class BuildDirManager;
|
2009-11-23 12:11:48 +01:00
|
|
|
};
|
|
|
|
|
|
2016-08-25 14:33:44 +02:00
|
|
|
class CMakeProjectImporter;
|
|
|
|
|
|
2019-01-29 08:55:52 +01:00
|
|
|
class CMakeBuildConfigurationFactory : public ProjectExplorer::BuildConfigurationFactory
|
2010-01-07 18:17:24 +01:00
|
|
|
{
|
|
|
|
|
Q_OBJECT
|
|
|
|
|
|
|
|
|
|
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
|
|
|
CMakeBuildConfigurationFactory();
|
2010-01-07 18:17:24 +01:00
|
|
|
|
2017-02-07 16:23:36 +01:00
|
|
|
enum BuildType { BuildTypeNone = 0,
|
|
|
|
|
BuildTypeDebug = 1,
|
|
|
|
|
BuildTypeRelease = 2,
|
|
|
|
|
BuildTypeRelWithDebInfo = 3,
|
|
|
|
|
BuildTypeMinSizeRel = 4,
|
|
|
|
|
BuildTypeLast = 5 };
|
|
|
|
|
static BuildType buildTypeFromByteArray(const QByteArray &in);
|
|
|
|
|
static ProjectExplorer::BuildConfiguration::BuildType cmakeBuildTypeToBuildType(const BuildType &in);
|
|
|
|
|
|
2019-01-29 16:51:17 +01:00
|
|
|
QList<ProjectExplorer::BuildInfo> availableBuilds(const ProjectExplorer::Target *parent) const override;
|
|
|
|
|
QList<ProjectExplorer::BuildInfo> availableSetups(const ProjectExplorer::Kit *k,
|
|
|
|
|
const QString &projectPath) const override;
|
2012-04-24 15:49:09 +02:00
|
|
|
|
|
|
|
|
private:
|
2019-01-29 16:51:17 +01:00
|
|
|
ProjectExplorer::BuildInfo createBuildInfo(const ProjectExplorer::Kit *k,
|
|
|
|
|
const QString &sourceDir,
|
|
|
|
|
BuildType buildType) const;
|
2016-08-25 14:33:44 +02:00
|
|
|
|
|
|
|
|
friend class CMakeProjectImporter;
|
2010-01-07 18:17:24 +01:00
|
|
|
};
|
2009-11-23 13:29:45 +01:00
|
|
|
|
|
|
|
|
} // namespace Internal
|
|
|
|
|
} // namespace CMakeProjectManager
|