I’ve seen that replacing linux-g++ in the .pro with linux-g++-32 now I can compile for x86.

What should I put in .pro for arm ?

I found a possible problem.

In Qt Creator -> Projects -> Build Steps

there is:

so it seems always take linux-g++-32 for every toolchain I select.

I solved the problem removing the wron build step and adding a new “Custom Process Step”:

Command: /opt/qt4-4.7.4-beagle/bin/qmake
Command arguments: /home/luca/DATI/gei/qt4/progetto_solarwind/satellite/satellite_2/satellite/satellite.pro

and putting this build step on the top of the build steps.

Is there another way to change the default:

I found a Bug Report:

https://bugreports.qt.nokia.com/browse/QTCREATORBUG-5917

So I hope it will be solved soon …

You can leave the qmake build step. Just expand it and you will find an input field for command line switches. If you add “-spec name-of-your-spec” to it, the default is replaced by your value.

You can vote for QTCREATORBUG-5756 [bugreports.qt.nokia.com], this is the replacement report for QTCREATORBUG-5756 [bugreports.qt.nokia.com].

Thnaks Volker,
I just tried and it works.

I seen that before writing the “additional aruments” the “Effective qmake call” was:

next when typing “-spec linux-g++” the “Effective qmake call” become:

For me it should be better to avoid at all the argument “-spec” to let Qt to get the “default”.
Do you think it’s possible?

As far as I know, the Trolls are on it. You can vote for QTCREATORBUG-5756 [bugreports.qt.nokia.com], that could rise the priority :-)

Ok, I just voted it…

Thanks again.

usually i use linux-g++*

Volker wrote:

You can leave the qmake build step. Just expand it and you will find an input field for command line switches. If you add “-spec name-of-your-spec” to it, the default is replaced by your value.

You can vote for QTCREATORBUG-5756 [bugreports.qt.nokia.com], this is the replacement report for QTCREATORBUG-5756 [bugreports.qt.nokia.com].

I just found another workaround to use the default spec instead of using “-spec name-of-your-spec” I only need “-spec default”.

Try the master branch: That should override the spec file way less often. I would really appreciate your feed back: Do the changes improve the situation for you guys?

Tobias Hunger wrote:

Try the master branch: That should override the spec file way less often. I would really appreciate your feed back: Do the changes improve the situation for you guys?

Sorry Tobias,
I didn’t understand very well what you mean with “try the master branch”?
If you can explain me better I can try.

Luca wrote:

Sorry Tobias, I didn’t understand very well what you mean with “try the master branch”? If you can explain me better I can try.

He meant to use the sources of Qt Creator at gitorious [qt.gitorious.org]. You would have to checkt out the master branch and build Creator manually. To my knowledge, there are no nightly builds or similar prebuilt development snapshots available.

I tried the Qt Creator compiled from qt.gitorious.org .
Now there is:

It should be better to have nothing as default spec .

What system are you working on? I guess a intel based Linux? 64bit or 32bit?

What kind of system are you developing for?

I’m working on a Slackware Linux 13.37 (32 bit) and I’m developing for the same system and for a BeagleBoard xM (Angstrom OS).