[Qt-creator] Kits in QtCreator 2.6

[Diego Iastrubni]

Hi Tobias (and Eike... see bllow),


On Wed, Sep 12, 2012 at 12:32 PM,  <tobias.hunger at nokia.com> wrote:
>> * From now on, you need to specify the full path for cmake on linux. WHY?
> That is unrelated to Kits.

Who cares, then ignore my email subject and we are on-topic again... ;)

I will try reproduce and fix.

> On linux it should pick up compilers in PATH. It will also auto-detect MSVC
> on windows and does some limited probing for mingw. We do not support
> icc on windows AFAIK.
>
> The compiler detection is exactly (minus some fixes here and there) what we
> did in earlier versions.
..
> Again the qmake in PATH should have been picked up. That should cover most
> linux users. Windows users are most often out of luck here.
...
> If there is no kit defined at all then it should have set up a desktop
> kit for you, filling in a Qt version and matching tool chain for you.
>
> Looks like the detection of those failed for you, so you were out of luck.
>
This failed on my setup: Debian Testing, CLang + GCC, all from
official repositories of debian. I think one of the triggers what
update by Debian from Qt 4.8.1 to Qt 4.8.2. This is the reason I ask
for a "panic button".

Since I have both versions of QtCreator (2.5, 2.6 and master... 2
versions...) I assume I can test this. I will re-test and report what
exactly went wrong.

>> * You still default to build using a single process. IMHO you can
>> detect the number of processors and execute add "-j $CPU" to the make
>> command arguments.
>
> Using parellel build or not is something a developer should decide IMHO. There
> are enough build systems out there that can not cope with that (getting fewer thanks
> to multi-core systems:-).

QtCreator supports cmake and qmake. Both support for multi-process
compilations. If someone is using a stand alone Makefile (I did for a
year on another non Qt related project, so from the user point of view
I really know how QtCreator behaves), he will have to know what he is
doing, lets ignore this scenario.

Again - when using cmake/qmake: please add the default parameters to
make. This makes compilation 4-8 time faster.


Eike Ziller also wrote:
>> * A reset button for this whole thing would be nice: delete
>> everything, and detect whatever is possible.> A way to add a Kit with simply all defaults from your PATH would be beneficial.
> Like it is done the first time you start Qt Creator

Or migrating from previous version. Like I did this week.