The host system will not be taken into account, so the cross build
toolchains are also detected.
Task-number: QTCREATORBUG-10998
Change-Id: I04a410bbf368898b70d9560d2c2a4a6c60ed0b61
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Replace boolean "autodetect" by an enumeration with a value
AutoDetectionFromSettings indicating whether the Autodetection
originates from a settings file. Enable the "Remove" button for
those cases.
Currently, there is no way to remove toolchains that were once
autodetected and are no longer present. This happens for example
when working in different MinGW environments, which then
clutter up the toolchain options page and dramatically slow
down the options page opening since gcc is launched to query
the flags, etc.
Change-Id: I731168d8694fe56f60d909f9779f83cffa55fd44
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
The settings in the plugin manager (local/global) are where the plugin
manager is supposed to look for its settings, which has per se nothing
to do where Qt Creator wants other settings to be written to.
All Qt Creator code should use ICore::settings() for that instead.
Change-Id: I28bd855ae6cbcdf8d19017eb44f178e4624a1a61
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
This is after plugins have been shutdown. The toolchains are saved on
shutdown anyway.
Change-Id: I7d84c3c4538f27aa3f4c7c2677307de49621d641
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
This helps getting the plugin initialization right.
Change-Id: Id67508fe2d188132ca16ab8cca808a8c11080fa3
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Improve isValid for GccToolChain and MsvcToolChain to make that sane.
Change-Id: If45cdb4e2666dd1a2ee16c01cb65427362ec29da
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Do not delete auto-detected tool chains that are still found on the
system if they are not auto-detected again. This avoids kits loosing
toolchain information when the PATH variable changes.
Change-Id: Ibb91a0a3636828c3db40827bfe8b303502ce2a11
Reviewed-by: hjk <qthjk@ovi.com>
This is needed to catch any updates that were triggered during tear
down of the UI (which happens after the saveSettings signal was emitted).
Change-Id: I9f14e8807070f3192551a3653bad31072db539f5
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
We should be save already, but let's be paranoid...
Change-Id: I925fb94f4cebe4c54e3419e18d307a999055ebbf
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
This patch causes core dumps in my work-creator while it works fine
in my test creator. Revert till I find the reason for this.
This reverts commit 5d253b3704.
Change-Id: Ib9912cda15294c28b9136f79675e0e5694788d5b
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
We should be save already, but let's be paranoid...
Change-Id: I925fb94f4cebe4c54e3419e18d307a999055ebbe
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
This is to prevent throwing out tool chains the SDK wants to register.
Change-Id: Ia49552bcffd98cf4579784047f9a425b2279b83f
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
and not from Nokia/toolchains.xml. This makes sure the SDK settings
and the personal settings pathes differ in prefix only.
Change-Id: Ib3a742d28258e86912cb820ff6c9d0c1b44c1763
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
* Rename profiles to kits.
* Update some strings:
* projects mode has a Kits tab, not a Targets tab.
* " Settings" was dropped from the sub-tabs of the Kits tab
* menu entry "Build/Open Build/Run Target Selector" was renamed
to "Build/Open Build and Run Kits Selector".
* Use "Kit" instead of "Target" in miniprojecttargetselector.
(The class was not renamed as it does indeed select targets,
not kits)
Change-Id: I0727e086e2dfa0e8aaaf89fdc6f2e3596c7a4314
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
Do not save XML config files (profiles.xml, toolchains.xml, etc.)
if the file has not changed.
Change-Id: I5f0dea374b33a05e7c428f4031d53c83d92de595
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
Currently it contains compiler settings only, so there's no
need to let people search for e.g. debugger settings there,
that might be considered part of the toolchain, too.
Change-Id: I458f3d1cf1784b85820f8af7604a2a004372a909
Reviewed-by: hjk <qthjk@ovi.com>
MSVC warns about pm being unused (because settings() is static)
Change-Id: I750804cc52edc71649545bc03f798a6802c87c7d
Reviewed-by: Laszlo Papp <lpapp@kde.org>
Reviewed-by: hjk <qthjk@ovi.com>
Also removed all <QMainWindow> includes which are not needed
anymore.
Change-Id: I393c9a62a5c6df95d9f35d872e1473a4f13bcdc4
Reviewed-by: hjk <qthjk@ovi.com>
Introduce Profiles to store sets of values that describe a system/device.
These profiles are held by a target, getting rid of much of the information
stored in the Build-/Run-/DeployConfigurations, greatly simplifying those.
This is a squash of the wip/profile branch which has been on gerrit for a
while, rebased to current master.
Change-Id: I25956c8dd4d1962b2134bfaa8a8076ae3909460f
Reviewed-by: Daniel Teske <daniel.teske@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>
Save/Restore has been updated to reflect this:
We now save manual as well as auto-detected tool chains into the user
toolChains.xml file.
When loading we load the SDK as well as the user toolChains.xml files.
We then do a autodetection run. All the tool chains restored that are
marked up as auto-detected are then checked again:
* the tool chain was autodetected again: Throw away the newly auto-
detected tool chain and reuse the saved one. This makes sure we
keep the QUuid that is now part of the tool chains id.
* the tool chain was not autodetected again: Throw away the saved
tool chain.
* the tool chain was newly autodetected: Add the new tool chain
We keep the old id around in the legacyId() method. It is used when
loading old .user files only. So there is no need to implement this
method for new tool chains.
Task-number: QTCREATORBUG-6702
Change-Id: Ifc0a216e5351a8a57db03615ba329e355e7d5f59
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
