Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. [SOLVED] Qt 4.8.3 qmake produces faulty makefiles
Forum Updated to NodeBB v4.3 + New Features

[SOLVED] Qt 4.8.3 qmake produces faulty makefiles

Scheduled Pinned Locked Moved Installation and Deployment
5 Posts 2 Posters 3.4k Views 1 Watching
  • 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.
  • E Offline
    E Offline
    egrath
    wrote on last edited by
    #1

    Hi,
    I am currently trying to get Qt 4.8.3 and TDM-GCC running. Unfortunately not even a simple application is buildable because qmake produces defective Makefiles in my case.

    When i run mingw32-make in my shadow build tree, i get the following error

    @mingw32-make -f Makefile.Release
    mingw32-make[1]: Entering directory C:/Temp/test01-build-Desktop-Release' mingw32-make[1]: *** No rule to make target ../test01/...', needed by ui_mainwindow.h'. Stop. mingw32-make[1]: Leaving directory C:/Temp/test01-build-Desktop-Release'
    mingw32-make: *** [release] Error 2@

    The offending part of the Makefile.Release file is:

    @ui_mainwindow.h: ../test01/mainwindow.ui
    ../test01/...
    c:/Qt/4.8.3/bin/uic.exe ../test01/mainwindow.ui -o ui_mainwindow.h@

    Can anyone tell me what i'm doing wrong? The project i've used for this purpose is a Qt Creator 2.6 generated application (default "Qt GUI Application")

    What i've tried so far:

    Using another Compiler (Stock MinGW) => No success

    Manually running "qmake -makefile -spec win32-g++" in the shadow build directory => No success

    Manually running "qmake -makefile -speci win32-g++" in the source directory => No success

    Adding C:\Qt\4.8.3\bin and C:\MingW32\bin to the PATH variable => No success

    Tried Qt 4.8.1 instead => No success, same problem

    I am running out of ideas...

    Thanks,
    egrath

    1 Reply Last reply
    0
    • E Offline
      E Offline
      egrath
      wrote on last edited by
      #2

      After doing a little more investigation it seems that the issue must be related to the local system (Windows 8 RTM):

      Copying Qt 4.8.3 and the MinGW compiler to another host (Windows 7 based) and running qmake/mingw32-make there works.

      Running qmake on another host (Windows 7) and compiling the project on the Windows 8 box works too.

      1 Reply Last reply
      0
      • sierdzioS Offline
        sierdzioS Offline
        sierdzio
        Moderators
        wrote on last edited by
        #3

        Interesting. Consider trying out "Qt 4.8.4 RC3":http://releases.qt-project.org/digia/4.8.4_RC3/ and if the problem persists, would be nice to report this as a bug on "jira":https://qt-project.org/wiki/ReportingBugsInQt.

        (Z(:^

        1 Reply Last reply
        0
        • E Offline
          E Offline
          egrath
          wrote on last edited by
          #4

          So, after digging and playing around a little more i've found out whats going on - and it seems to be a bug in Qmake.

          I've set up my system to execute a batch script automatically every time i run "cmd.exe" via the Registry Key "HKCU\Software\Microsoft\Command Processor" REG_SZ AutoRun. If this batch script outputs something like
          @
          <BLANK LINE>
          Setting up environment ....
          <BLANK LINE>
          @

          in my case, the newlines and '...' end up in the Makefile. Automagically the alphanumeric characters are filtered out. As soon as i disable the output of the batch script, everything works as expected. Should i post a Bug report to JIRA or is this just a behavior too specific in my environment?

          Thanks,
          egrath

          1 Reply Last reply
          0
          • sierdzioS Offline
            sierdzioS Offline
            sierdzio
            Moderators
            wrote on last edited by
            #5

            This is indeed quite specific, but I think it's worth reporting. There are some generally available programs that hook up to cmd.exe, too, so a fix might have some broader use.

            (Z(:^

            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