Setting up a qbs profile, particularly for Qt, can take a measurable
amount of time, so we should not do bulk changes via the kitsChanged()
signal. Instead:
- For the initial kit loading, delay the profile setup until
the kit is needed for the first time, i.e. the user attaches it
to a project.
- Handle adding, removing and updating a kit separately; in
particular, do not do anything to other kits.
Change-Id: If09d3c40b21e9a1356dc96089b92a60186a9bcdb
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
And capitalization of product name.
Change-Id: Ia021a389dfd3e82a1b09a6e56ba721707013d64a
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
And do the necessary adaptation in the Qbs project manager, namely
giving the qbs::Settings object a base directory. The respective change
in the qbs API is necessary for being able to run more than one QtC
instance at the same time without ill effects.
Change-Id: I6859a6616bd744915aa21c3f07b6c45243899de5
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
This was simply forgotten, leading to semi-random behavior in the
profile setup code (e.g. a Qt 4 version being treated like a Qt 5 one).
Change-Id: I6d75cf3c622a0dd520724b25eb9b823d3dcc117d
Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
Reviewed-by: Jake Petroules <jake.petroules@petroules.com>
Includes some necessary adaptations to the QbsProjectManager plugin,
namely:
- Use the new library for setting up Qt profiles.
- Use per-profile preferences.
Change-Id: I0a639bd291d790c6da9cb4ade53841314310d5ef
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
No need to poke around in the settings directly.
Change-Id: I689039a0cb0afd2e3a4c32b2108755d79c8fb4b6
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Provide a way for plugins to extend the profiles that Creator
will write into the Qbs configuration.
This should allow e.g. the Android plugin to add customized settings.
Change-Id: I0de596e2c922280b953c43ea0651b08b8936234c
Reviewed-by: BogDan Vatra <bogdan@kde.org>
* targetOS for mac is "osx"
* targetOS and toolchain are lists
Change-Id: I53d6c0d3669570c5c35f42a358727128d4d9d827
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
Move logic to detect already open projects into ProjectExplorer itself,
along with some check for the canonicalFilePath.
Remove the same logic from the individual projectmanagers.
Put check that the path is a file into project managers. So far all of
them assume the project file to be a file (e.g. a xcode project manager
would expect a directory though).
Task-number: QTCREATORBUG-9350
Change-Id: I3901958395e3c594c8cfba9a85dc7d3ec3334afb
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
qbs.mkspecPath contains the full path to the mkspec,
not the directory containing all mkspecs.
Change-Id: I9407057eff0c587bcc44d393bf4eede1d4263d65
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Set QBS_LOG_LEVEL to any number, the higher the more messages you
will get.
Change-Id: I6ae0d3a5bb94ad6865cd57d9ff381d36c8c8e95e
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
