Allow to query the DeviceFactory for device types it can create as
well as the display names to use for those types. Also allow to
create any of the supported device types.
The MaddeDeviceFactory makes use of the information to set the correct
type in the wizard.
Change-Id: I8c05ecd467e5bb1b151a84a8d62ef98a57849605
Reviewed-by: Christian Kandeler <christian.kandeler@nokia.com>
By listening to the signal updated() instead of deviceListChanged() we
can't simplify the update. updated() is also emitted when devices are
added or removed.
Change-Id: Ife985f420e2a2904d65185148d0db38b7367b3fd
Reviewed-by: Christian Kandeler <christian.kandeler@nokia.com>
Use Core::Id for all the project related objects in favor of plain
QStrings.
Change-Id: I790ab40cb29899efdb49c413a77609486f52e683
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
Allow DCs to be enabled/disabled.
Add infrastructure to target to propagate enabled signals of
BCs, RCs and DCs.
Change-Id: I8ae27a943953228b18e61396a22a2d7a2e4e9694
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>
The supported targets don't change, it is which targets can be created
Change-Id: I0a454281c061457d23f3a9c2ec1d2a6bd6484474
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>
Getting the #include directives ready for Qt5. This includes the
new-project wizards.
Change-Id: Ia9261f1e8faec06b9285b694d2b7e9a095978d2b
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
This includes:
- decoupling deploy configurations from targets (Reviewed-by: dt)
- adding a "Generic Linux" device type
- splitting up the Maemo deployment step into small pieces that
can be combined in different ways (and much more easily maintained)
- adding a new version handler for pro.user files
(Reviewed-by: Tobias Hunger)
Also:
- Add and use an SSH manager class for easier connection sharing.
- Make the SSH connection parameters a fixed attribute of the connection.
Refactor ToolChains in Qt Creator:
* Allow for several toolchains of the same type
* Be smarter wrt. guessing what kind of output a toolchain
produces. This allows us to eventually handle e.g. embedded
linux setups way better than before.
* Be smarter wrt. guessing what kind of environment a Qt version
needs.
* Improve auto-detection of toolchains a bit
* Decide on which debugger to use based on the kind of output
produced by the compiler.
* Add options page to configure toolchains
* Remove toolchain related options from the Qt version dialog
Reviewed-by: dt
The build actions are disabled if the buildconfiguration is disabled.
The deploy and run actions are disabled if deploying or running invokes
building automatically.
Qt4BuildConfigurations are disabled while parsing.
Task-Nr: QTCREATORBUG-2576
Now that we have 2.0 out we can be less strict when checking
project consistency when loading .user files. The strictness
was necessary due to upgrading non-target projects to target
projects.
* Allow for invalid Qt versions when loading a .user file that was not
updated from the pre-target era.
* Update the UI to show invalid Qt versions as invalid. Remove
the Invalid version as soon as a valid one is imported.
This does preserve the buildsteps, too.
* Add a DeployConfiguration class to hold settings related
to deployment.
* Add BuildStepsList to hold a list of buildsteps
* Update BuildConfiguration to use BuildStepLists instead of
manageing lists of buildsteps itself.
* Update BuildManager to use BuildStepLists in its interfaces
* Fix fallout introduced by API changes
* Update .user file to new way of storing settings
Task-number: QTCREATORBUG-1427
Task-number: QTCREATORBUG-1428
Task-number: QTCREATORBUG-1811
Task-number: QTCREATORBUG-1930
* Ease cross device development by introducing 'targets' which
group build- and runsettings that are valid for this one target
Most of the kudos for the code review go to dt. Con, thorbjorn,
ckandler and others did also review parts of this patch.
Reviewed-by: dt
