2022-08-19 15:59:36 +02:00
|
|
|
// Copyright (C) 2016 The Qt Company Ltd.
|
2022-12-21 10:12:09 +01:00
|
|
|
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0-only WITH Qt-GPL-exception-1.0
|
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
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
#include "cmake_global.h"
|
2016-02-03 13:52:50 +01:00
|
|
|
#include "cmakeconfigitem.h"
|
|
|
|
|
|
2020-04-02 14:49:05 +02:00
|
|
|
#include <projectexplorer/buildaspects.h>
|
2009-11-23 12:11:48 +01:00
|
|
|
#include <projectexplorer/buildconfiguration.h>
|
2023-01-02 20:03:41 +01:00
|
|
|
#include <projectexplorer/environmentaspect.h>
|
2009-11-23 12:11:48 +01:00
|
|
|
|
2023-07-07 15:46:17 +02:00
|
|
|
#include <qtsupport/qtbuildaspects.h>
|
|
|
|
|
|
2009-11-23 13:29:45 +01:00
|
|
|
namespace CMakeProjectManager {
|
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 {
|
|
|
|
|
|
2019-10-25 09:55:32 +02:00
|
|
|
class CMakeBuildSystem;
|
2016-02-24 18:00:24 +01:00
|
|
|
class CMakeBuildSettingsWidget;
|
2021-02-04 14:53:42 +01:00
|
|
|
class CMakeProjectImporter;
|
|
|
|
|
|
2023-07-07 15:46:17 +02:00
|
|
|
class InitialCMakeArgumentsAspect final : public Utils::StringAspect
|
|
|
|
|
{
|
|
|
|
|
public:
|
|
|
|
|
InitialCMakeArgumentsAspect(Utils::AspectContainer *container);
|
|
|
|
|
|
|
|
|
|
const CMakeConfig &cmakeConfiguration() const;
|
|
|
|
|
const QStringList allValues() const;
|
|
|
|
|
void setAllValues(const QString &values, QStringList &additionalArguments);
|
|
|
|
|
void setCMakeConfiguration(const CMakeConfig &config);
|
|
|
|
|
|
|
|
|
|
void fromMap(const QVariantMap &map) final;
|
|
|
|
|
void toMap(QVariantMap &map) const final;
|
|
|
|
|
|
|
|
|
|
private:
|
|
|
|
|
CMakeConfig m_cmakeConfiguration;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
class ConfigureEnvironmentAspect final: public ProjectExplorer::EnvironmentAspect
|
|
|
|
|
{
|
|
|
|
|
public:
|
|
|
|
|
ConfigureEnvironmentAspect(Utils::AspectContainer *container,
|
|
|
|
|
ProjectExplorer::BuildConfiguration *buildConfig);
|
|
|
|
|
|
|
|
|
|
void fromMap(const QVariantMap &map);
|
|
|
|
|
void toMap(QVariantMap &map) const;
|
|
|
|
|
};
|
|
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
} // namespace Internal
|
2009-11-23 13:29:45 +01:00
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
class CMAKE_EXPORT CMakeBuildConfiguration : public ProjectExplorer::BuildConfiguration
|
2009-11-23 12:11:48 +01:00
|
|
|
{
|
2009-11-25 18:49:59 +01:00
|
|
|
Q_OBJECT
|
2010-01-18 12:11:04 +01:00
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
public:
|
2020-06-26 13:59:38 +02:00
|
|
|
CMakeBuildConfiguration(ProjectExplorer::Target *target, Utils::Id id);
|
2021-02-04 14:53:42 +01:00
|
|
|
~CMakeBuildConfiguration() 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
|
|
|
|
2019-05-28 13:49:26 +02:00
|
|
|
static Utils::FilePath
|
|
|
|
|
shadowBuildDirectory(const Utils::FilePath &projectFilePath, const ProjectExplorer::Kit *k,
|
2016-03-01 14:12:35 +01:00
|
|
|
const QString &bcName, BuildConfiguration::BuildType buildType);
|
CMake: iOS: Enable automatic provisioning updates
By default xcodebuild does not try create / download a provisioning
profile for a project if a valid one does not exist locally
in ~/Library/MobileDevice/Provisioning Profiles, even if the
Xcode CODE_SIGN_STYLE attribute is set to Automatic.
Starting with Xcode 9, xcodebuild accepts a new
-allowProvisioningUpdates option.
When passed, xcodebuild will request a new provisioning profile
from Apple's servers for the current project and use it during
the build. The provisioning profile is only needed when building
for a real device, not the simulator.
When building an iOS project with qmake, the option is embedded in the
wrapping Makefile generated by qmake, so Qt Creator can simply call
make (which it does).
For CMake, there is no wrapping Makefile, so we need to pass the new
option explicitly as an additional build tool argument.
There might be cases where automatic provisioning is not desired,
which is why there is now a new checkbox in the CMake build step
configuration widget. It's default value is 'enabled', to match
qmake's behavior.
As an implementation detail, isiOS had to be moved to a header file so
it's accessible to both the build configuration and the build step.
Fixes: QTCREATORBUG-26246
Change-Id: Ic80cd965ba095d0ff379e13ad2ffb8c298c9f7c4
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
2022-05-05 16:26:11 +02:00
|
|
|
static bool isIos(const ProjectExplorer::Kit *k);
|
CMake: Make QML debugging state reflect build system state
After parsing the CMake response, we make the configuration variables
table reflect the actual configuration in the build directory. It is one
of our "promises" that we do not break an existing build configuration,
to avoid unexpected rebuilds.
This was not quite true for the "QML debugging and profiling" setting.
When that setting and the actual build directory disagreed, the user
would get a dialog asking for running CMake with additional parameters,
and when running CMake via the button in projects mode or the menu, it
would just change these configuration parameters, potentially leading to
an unexpected complete rebuild of the application.
So, after parsing check if the actual CMake configuration matches our
QML debugging setting, and if not, change the setting to "Leave at
Default", to ensure that we don't mess with the build.
Fix the "Run CMake" button state (in the "Current Configuration") when
changing the QML debugging option, which should become bold, if the
CMake parameters change.
Amends 2577ce8ba1a69ad716c2fc2a5d0d5cc742c3c4cf and fixes the drawback
mentioned there, i.e. setting the build directory of a "Debug" build
configuration to an existing build directory with QML debugging
disabled, will now simply set the QML debugging option to "Leave at
Default" instead of forcing it to "Enabled".
Change-Id: Ie6d4875d59319687d94e44e459ca76038e5813c0
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
2022-06-07 10:18:34 +02:00
|
|
|
static bool hasQmlDebugging(const CMakeConfig &config);
|
2016-03-01 14:12:35 +01:00
|
|
|
|
2016-11-14 15:18:25 +01:00
|
|
|
// Context menu action:
|
|
|
|
|
void buildTarget(const QString &buildTarget);
|
2019-10-25 09:55:32 +02:00
|
|
|
ProjectExplorer::BuildSystem *buildSystem() const final;
|
|
|
|
|
|
2022-06-15 14:40:23 +02:00
|
|
|
void addToEnvironment(Utils::Environment &env) const override;
|
|
|
|
|
|
2022-08-10 19:12:40 +02:00
|
|
|
Utils::Environment configureEnvironment() const;
|
2023-07-07 16:27:46 +02:00
|
|
|
Internal::CMakeBuildSystem *cmakeBuildSystem() const;
|
2022-08-10 19:12:40 +02:00
|
|
|
|
2023-07-07 15:46:17 +02:00
|
|
|
ProjectExplorer::BuildDirectoryAspect buildDir{this};
|
|
|
|
|
Internal::InitialCMakeArgumentsAspect initialCMakeArguments{this};
|
|
|
|
|
Utils::StringAspect additionalCMakeOptions{this};
|
|
|
|
|
Utils::FilePathAspect sourceDirectory{this};
|
|
|
|
|
Utils::StringAspect buildTypeAspect{this};
|
|
|
|
|
QtSupport::QmlDebuggingAspect qmlDebugging{this};
|
|
|
|
|
Internal::ConfigureEnvironmentAspect configureEnv{this, this};
|
|
|
|
|
|
2016-02-11 16:33:15 +01:00
|
|
|
signals:
|
2021-02-04 14:53:42 +01:00
|
|
|
void signingFlagsChanged();
|
2022-08-10 19:12:40 +02:00
|
|
|
void configureEnvironmentChanged();
|
2021-02-04 14:53:42 +01:00
|
|
|
|
|
|
|
|
protected:
|
|
|
|
|
bool fromMap(const QVariantMap &map) override;
|
2016-02-11 16:33:15 +01:00
|
|
|
|
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;
|
|
|
|
|
|
|
|
|
|
ProjectExplorer::NamedWidget *createConfigWidget() override;
|
|
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
virtual CMakeConfig signingFlags() const;
|
2017-04-07 11:15:26 +02:00
|
|
|
|
2022-09-05 20:09:12 +02:00
|
|
|
void setInitialBuildAndCleanSteps(const ProjectExplorer::Target *target);
|
|
|
|
|
void setBuildPresetToBuildSteps(const ProjectExplorer::Target *target);
|
2023-07-07 16:27:46 +02:00
|
|
|
void filterConfigArgumentsFromAdditionalCMakeArguments();
|
2022-09-05 20:09:12 +02:00
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
Internal::CMakeBuildSystem *m_buildSystem = nullptr;
|
2016-02-24 18:00:24 +01:00
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
friend class Internal::CMakeBuildSettingsWidget;
|
|
|
|
|
friend class Internal::CMakeBuildSystem;
|
2009-11-23 12:11:48 +01:00
|
|
|
};
|
|
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
class CMAKE_EXPORT CMakeBuildConfigurationFactory
|
|
|
|
|
: public ProjectExplorer::BuildConfigurationFactory
|
2010-01-07 18:17:24 +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
|
|
|
CMakeBuildConfigurationFactory();
|
2010-01-07 18:17:24 +01:00
|
|
|
|
CMake: Add 'Profile' configuration
Get rid of the hardcoded QML Debugging for Debug & RelWithDebInfo from
the project template, because RelWithDebInfo is actually a good
configuration for doing releases (we use it for Qt Creator), and
enabling QML debugging for releases is a bad idea.
Instead enable QML Debugging in Qt Creator for the Debug configuration,
and add a 'Profile' configuration that is 'RelWithDebInfo + QML
Debugging'.
When importing a build, we only set the "QML debugging" option of the
build configuration, if it is enabled in the imported build, even if it
uses CMAKE_BUILD_TYPE=Debug .
One drawback: When not importing a build, but just setting the build
directory of a "Profile" or "Debug" configuration to an existing build,
Qt Creator asks if it should apply "-DCMAKE_CXX_FLAGS=-DQT_QML_DEBUG".
The user can choose not to, but then is asked the next time again, and
it is not obvious that the "QML debugging" option is responsible for
this.
That is somewhat orthogonal to this change though: Even without this
change, if the user changes the QML debugging option from "Leave at
Default" to "Enable", the same happens, and it is also not clear to the
user how to get rid of it. The user might not even have realized that
they changed the option (e.g. on platforms where the mouse wheel cycles
combo box values).
I think the correct solution is to 1. make clearer where the CMake flags
came from in that dialog, 2. allow the user to cancel a build from that
dialog, 3. allow the user to discard these changes (by changing the
setting) from that dialog. But that is for another patch.
Amends 3300182d405bffe062a0f2be900f35822a9e20b0
Amends 77fed0b0fdce2a93f465c20cd87c41900117dcda
Change-Id: I95de59473b67c5afd6a53ea7f49838dbaef770d4
Reviewed-by: Artem Sokolovskii <artem.sokolovskii@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
2022-05-18 10:40:31 +02:00
|
|
|
enum BuildType {
|
|
|
|
|
BuildTypeNone = 0,
|
|
|
|
|
BuildTypeDebug = 1,
|
|
|
|
|
BuildTypeRelease = 2,
|
|
|
|
|
BuildTypeRelWithDebInfo = 3,
|
|
|
|
|
BuildTypeProfile = 4,
|
|
|
|
|
BuildTypeMinSizeRel = 5,
|
|
|
|
|
BuildTypeLast = 6
|
|
|
|
|
};
|
2017-02-07 16:23:36 +01:00
|
|
|
static BuildType buildTypeFromByteArray(const QByteArray &in);
|
|
|
|
|
static ProjectExplorer::BuildConfiguration::BuildType cmakeBuildTypeToBuildType(const BuildType &in);
|
|
|
|
|
|
2012-04-24 15:49:09 +02:00
|
|
|
private:
|
2020-01-09 18:42:28 +01:00
|
|
|
static ProjectExplorer::BuildInfo createBuildInfo(BuildType buildType);
|
2016-08-25 14:33:44 +02:00
|
|
|
|
2021-02-04 14:53:42 +01:00
|
|
|
friend class Internal::CMakeProjectImporter;
|
2010-01-07 18:17:24 +01:00
|
|
|
};
|
2009-11-23 13:29:45 +01:00
|
|
|
|
|
|
|
|
} // namespace CMakeProjectManager
|