Important: Please read the Qt Code of Conduct -

Qt Creator not showing errors properly in "Issues" Pane

  • I'm using Qt Creator 3.0.1 with Qt 5.2.1 on a Mac. I installed my Qt using qt-opensource-mac-x64-ios-5.2.1.dmg and the build steps for the kits use qmake and make. My version of Xcode is 5.0.2. The problem happens when use the iphoneos or the iphonesimulator kits. It works correctly with the Desktop Qt 5.2.1 kit. I can duplicate the problem with the examples in addition to my own application.

    The problem is the build errors aren't being displayed properly in the "Issues" pane. Instead it just says [iphoneos-release] Error 65. I have to keep bringing up the Compile Output Pane and scroll around to see the errors. I can still find and fix the bugs it is just very time consuming.

    From reading a previous post from an older version of Qt Creator, I've learned that the Creator probably doesn't recognize my language as it parses the compile output. Setting LC_MESSAGES to en_EN.UTF-8 or LANG to en_EN.UTF-8 doesn't help and yes the text is in English.

    No one else seems to be complaining about this so I assume it's a problem with my installation or settings.

    Any ideas on how I can fix my problem would be greatly appreciated.

  • Hey all,
    No one has responded so let me ask this question another way. Does anyone have this working or is it a current limitation with the iPhone configuration?

    So is anyone out there using Qt Creator 3.0.1 with Qt 5.2.1 on a Mac with Xcode 5.0.2 and building for the iPhone and/or the iPhone Simulator? If you are, do you see your compile errors in the "Issues" pane and can you double select these compile bugs to bring up the file at the correct line?

    Or is there anyone out there that is having the same problem as me?

    Once again what I have to do is go over to the "Compile Output" pane, scroll up to find the errors then load the file and scroll to the line number myself to determine each and every error.

    Thanks in advance for any insight.

  • Lifetime Qt Champion

    Hi and welcome to devnet,

    IIRC, error 65 might come from the fact that your are trying to build c++11 code which is not enabled by default in Qt 5.2 for iOS.

    Do you also have that if you build a simple default application ?

  • SGaist, thanks for responding.

    Yes I have this same problem with the examples. I can switch over to the Desktop Qt 5.2.1 clang 64bit kit without changing anything else and the compile errors do show up and work as expected in the "Issues" pane. The example I just brought up to verify this is the address book.

    I didn't explicitly set it up to use C++11 but I still went into one of the generated makefiles and searched for c++11 and did not find it set.

    The following are set:
    CC = clang
    CXX = clang++

    and there are NO CXXFLAGS set that have c++11 set such as
    QMAKE_CXXFLAGS+= -std=c++11 or
    QMAKE_LFLAGS += -std=c++11

    Any other suggestions on things to check?

    Thank you, thank you for any help,

  • Lifetime Qt Champion

    For the panel issue, you should check the "bug report system": to see if it's something known.

    That looks good. Can you check against which of libc++ or libstdc++ you are linking against. If it's the former you should try with the later

  • Thanks again SGaist.

    I am using libstdc++ so that isn't the problem.

    I did look at the bugs on the link you gave me and this was a bug in Qt Creator 2.6.1. The problem was caused by colors in the "Compile Output" pane which caused the AnsiFilterParser to not work. This was supposedly fixed back in Sept 2013.

    I do have color in my compile output pane so I guess this could still be the problem with Qt Creator 3.0.1 although the Desktop Qt 5.2.1 clang 64bit has color and it works. At any rate I thought it'd be useful to try and turn off the color and see if it helped.

    When I search a way to turn off the color I see " If I modify the .pri to give -fno-color-diagnostics, then Creator sees the issues properly." Can you make sense out of this? I think they are setting something in the .pri file to turn off the color in the error messages but I can't find any more information and this isn't telling me enough. Thoughts?

    Thanks again for any help and I still wonder if anyone out there has this working?

  • Lifetime Qt Champion

    It means that they add a the compiler flag -fno-color-diagnostic in their project file. Something like:

    @QMAKE_CXXFLAGS += -fno-color-diagnostic@

Log in to reply