Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

QtSDK 1.1.3 && toolchain problem



  • Hi all,
    I installed the new SDK and I'm trying to compile one my old project.

    The .pro has :
    @
    ....
    ....
    linux-g++ {
    INCLUDEPATH += ../modbus_x86
    QMAKE_LIBDIR += ../modbus_x86
    LIBS += -lmodbus
    }

    linux-arm-gnueabi-g++ {
    INCLUDEPATH += ../modbus_beagle
    QMAKE_LIBDIR += ../modbus_beagle
    LIBS += -lmodbus
    }
    ....
    ....
    ....
    @

    While compiling for x86 it doesn't find modbus.h . But the file is ../modbus_x86 .
    It seems that linux-g++ isn't recognized.

    I hadn't this problem with old SDK.

    How can I solve the problem?



  • 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:
    @
    qmake: qmake satellite.pro -r -spec linux-g++-32
    @

    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:
    @
    qmake: qmake satellite.pro -r -spec linux-g++-32
    @
    in the Build Steps?



  • 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":https://bugreports.qt.nokia.com/browse/QTCREATORBUG-5756, this is the replacement report for "QTCREATORBUG-5756":https://bugreports.qt.nokia.com/browse/QTCREATORBUG-5917.



  • Thnaks Volker,
    I just tried and it works.

    I seen that before writing the "additional aruments" the "Effective qmake call" was:
    @
    qmake /home/luca/DATI/gei/qt4/progetto_solarwind/satellite/satellite_2/satellite/satellite.pro -r -spec linux-g++-32
    @

    next when typing "-spec linux-g++" the "Effective qmake call" become:
    @
    qmake /home/luca/DATI/gei/qt4/progetto_solarwind/satellite/satellite_2/satellite/satellite.pro -r -spec linux-g++
    @

    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":http://bugreports.qt.nokia.com/browse/QTCREATORBUG-5756, that could rise the priority :-)



  • Ok, I just voted it...

    Thanks again.



  • usually i use linux-g++*



  • [quote author="Volker" date="1315518661"]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":https://bugreports.qt.nokia.com/browse/QTCREATORBUG-5756, this is the replacement report for "QTCREATORBUG-5756":https://bugreports.qt.nokia.com/browse/QTCREATORBUG-5917.[/quote]

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


  • Moderators

    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?



  • [quote author="Tobias Hunger" date="1316288453"]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?[/quote]

    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.



  • [quote author="Luca" date="1316334754"]
    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.[/quote]

    He meant to use the sources of Qt Creator at "gitorious":https://qt.gitorious.org/qt-creator. 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:
    @
    -spec linux-g++
    @
    as default choice.

    It should be better to have nothing as default spec .


  • Moderators

    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).



  • It still does not work with version 2.3.1. I updated the bug report.

    I tried to compile master from git several times but it failed with compilation errors, so I cannot comment on this version.


  • Moderators

    Volker: There were only critical bug fixes with a minimal chance to break unrelated things in 2.3.1. There was only very little QA possible in such a short time, so we could not retest everything.

    That made it too risky for me to change the tool chains for 2.3.1. Sorry.



  • Ah, ok. Then sorry for re-opening the issue in this case. I'll check out on the 2.4 beta as soon as it's out.



  • Just for the records:
    It's still not working in 2.4 beta.



  • Tobias promised to solve this problem in 2.5. We discussed this on qt-creator mailing list.


Log in to reply