Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. G++ error output not being shown
QtWS25 Last Chance

G++ error output not being shown

Scheduled Pinned Locked Moved Qt Creator and other tools
6 Posts 2 Posters 4.6k 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.
  • C Offline
    C Offline
    certdev
    wrote on last edited by
    #1

    I am evaluating Qt Creator 2.0.0 (based on Qt 4.7.0 32-bit) on Windows Vista.

    I have a problem where none of the compile errors (i.e. typos etc.) are being shown in either the "Compile Output" or the "Build Issues" panes.

    This seems to be true of all projects and persists despite a clean install of Qt Creator.

    I seem to be suffering a lot of permission errors when overwriting files (i.e. app.exe) which can usually only be solved by deleting the old version of the file. I wonder if this is a similar problem and that the g++ output is being redirected to a file which cannot be created?

    Thanks for any help

    1 Reply Last reply
    0
    • C Offline
      C Offline
      certdev
      wrote on last edited by
      #2

      Oh no, this is looking like a nasty Vista issue...

      From a cmd window there seems to be a problem with STDERR redirects:

      @mingw32-make@

      All compile errors are shown

      @g++ -c -g ....etc..... test.cpp@

      All compile errors are shown

      @g++ -c -g ....etc..... test.cpp 2> err.log@

      All compile errors are written to err.log

      @mingw32-make 2> err.log@

      only

      mingw32-make[1]: *** [debug/test.o] Error 1
      mingw32-make: *** [debug] Error 2

      is written to err.log

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

        Our parser expects gcc errors to show up on stderr. Some build systems seem to redirect it to stdout, thus breaking the parser. I already had one user report such an issue to the Qt Creator mailing list.

        Which kind of project are you building? This sounds like a custom makefile based one, is that correct?

        1 Reply Last reply
        0
        • C Offline
          C Offline
          certdev
          wrote on last edited by
          #4

          Thanks for the reply.

          I installed the whole system Qt SDK for Windows binary (setup file) from the qt.nokia.com downloads.

          This problem applies to any project and no custom makefile. I have only just installed Qt Creator (clean install, default options) and trying to build the examples/demos from within the IDE.

          The only thing slightly unusual about my system is that I have Xming installed (but not running).

          In a way I don't think its a Qt Creator problem as further investigation shows that the same thing happens on the command line as well.

          It seems that the STDERR output of child processes are not being redirected properly. So when running g++ directly STDERR can be redirected, but when mingw32-make spawns g++ then only the make errors are being redirected.

          I found this patch from Microsoft "http://support.microsoft.com/kb/971163":http://support.microsoft.com/kb/971163 but it only applies to Vista 64-bit (I am running 32-bit).

          Otherwise I have Google'd extensively for STDERR redirection problems on Vista but no luck so far.

          Thanks for any insight, maybe I should try to post on the mingw forums.

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

            Building with mingw works for me and I do see errors and warnings in the build issue pane.

            I am testing on Windows7 (64bit).

            1 Reply Last reply
            0
            • C Offline
              C Offline
              certdev
              wrote on last edited by
              #6

              Unfortunately I don't know what I changed exactly, but the errors are now shown as expected.

              It may have something to do with Xming capturing the redirected output.

              I was hoping to isolate the cause in case others suffered the same problem.

              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