Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. [SOLVED] Qt Creator 2.4.1 and gdb compile errors

[SOLVED] Qt Creator 2.4.1 and gdb compile errors

Scheduled Pinned Locked Moved General and Desktop
4 Posts 2 Posters 2.4k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W Offline
    W Offline
    winkle99
    wrote on last edited by
    #1

    Hi guys,

    I've looked all over for this and can't find an answer. Hope you can help.

    A hard drive failure forced me to do a couple of upgrades. I was using Qt Creator 2.3 and my compile errors and warnings were being displayed in the "Issues Tab", which is really convenient. However, when I upgraded to 2.4.1 this feature stopped working. I can't find a reference for what I need to do to get this working again. Can someone give me a hint as to what I need to reset. I've looked at the options and don't see anything obvious that I missed.

    Can someone point me in the right direction?

    Thank you,

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobias.hunger
      wrote on last edited by
      #2

      The tool chain decides how the output is parsed, so you need to make sure to have selected the correct tool chain for your project.

      1 Reply Last reply
      0
      • W Offline
        W Offline
        winkle99
        wrote on last edited by
        #3

        I double checked my Tool Chain and the correct compiler is there and being called however the compile errors are still not going to the Issues Tab. I tried splitting std::err and std::out on the General tab on the Build&Run Options dialog and this had no effect.

        1 Reply Last reply
        0
        • W Offline
          W Offline
          winkle99
          wrote on last edited by
          #4

          Discovered that my company has switched to ninja which does not send its out put to stderr. The guy who sets up our build system had added a wrapper to pipe the output back to stderr but forgot to re-install the wrapper after my system had to be rebuilt. (He also forgot to mention the wrapper at all.)

          Thanks to all who tried to help.

          1 Reply Last reply
          0

          • Login

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups
          • Search
          • Get Qt Extensions
          • Unsolved