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. Failed to parse default paths from copiler output
Forum Updated to NodeBB v4.3 + New Features

Failed to parse default paths from copiler output

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
7 Posts 3 Posters 3.7k 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.
  • N Offline
    N Offline
    NickM
    wrote on 12 Apr 2020, 11:58 last edited by
    #1

    I'm currently working with QT5.12.1 on Windows 10, and when I create a new blank project, I get the following message in QTCreators console:

    Running Windows Runtime device detection.
    No winrtrunner.exe found.
    C:/Qt/Qt5.12.1/5.12.1/mingw73_64/mkspecs/features/toolchain.prf(76): Variable QMAKE_CXX.COMPILER_MACROS is not defined.
    Project ERROR: failed to parse default search paths from compiler output
    Error while parsing file C:\Qt\Test\Proj\Proj.pro. Giving up

    I've inspected toolchain.prf and notice that this error message originates from the following line:

    isEmpty(QMAKE_DEFAULT_LIBDIRS)|isEmpty(QMAKE_DEFAULT_INCDIRS):
    !integrity:
    error("failed to parse default search paths from compiler output")

    Does anyone have any ideas why either of these two variables are not being set?
    Note: If I try to build the project (in QTCreator), close it and then open it again, it all works normally.
    Also, I have multiple versions of MSVC on my machine, but am building using a MINGW kit. I suspect the problem is rooted in this, because I can get the exact same QT setup to work on a near-identical windows machine, only without MSVC on it.

    1 Reply Last reply
    0
    • N Offline
      N Offline
      NickM
      wrote on 27 Apr 2020, 19:40 last edited by
      #2

      OK, well I've gotten a little closer to solving this. I know what is going wrong, but I don't know why. On my laptop and desktop I have identical installations of QT and QtCreator. The desktop is the problematic installation. Here's where the problem arises:
      If open QtCreator and Create a New Project, under C:\Qt\TempProj\ and I name the file "TempProj", My Laptop will create the following build directories by default:
      Kits01.JPG
      If I follow the EXACT same procedure (to the keystroke) my desktop will present me with the following default project directories:
      Kit02.JPG

      If I ignore the warnings and proceed, I get the error message above, QT can't find the course code, I can't build anything, etc.
      If I manually "correct" the build path so that it does not use the Nest"TestProj" path in the build target... I still see the error message above. But if I attempt a build (forcing it to build the actual path) and then navigate to that folder via "Projects>>Build Directory" Qt is suddenly aware of the source code and everything works as it should.

      I appreciate that this is an odd problem, but it's annoying to have to do this little dance each time I want to create a new project and for the life of me, I can't work out why two identical installations of QT make two different default build paths.

      So if anyone has any ideas, that would be appreciated.

      J 1 Reply Last reply 28 Apr 2020, 05:07
      0
      • N NickM
        27 Apr 2020, 19:40

        OK, well I've gotten a little closer to solving this. I know what is going wrong, but I don't know why. On my laptop and desktop I have identical installations of QT and QtCreator. The desktop is the problematic installation. Here's where the problem arises:
        If open QtCreator and Create a New Project, under C:\Qt\TempProj\ and I name the file "TempProj", My Laptop will create the following build directories by default:
        Kits01.JPG
        If I follow the EXACT same procedure (to the keystroke) my desktop will present me with the following default project directories:
        Kit02.JPG

        If I ignore the warnings and proceed, I get the error message above, QT can't find the course code, I can't build anything, etc.
        If I manually "correct" the build path so that it does not use the Nest"TestProj" path in the build target... I still see the error message above. But if I attempt a build (forcing it to build the actual path) and then navigate to that folder via "Projects>>Build Directory" Qt is suddenly aware of the source code and everything works as it should.

        I appreciate that this is an odd problem, but it's annoying to have to do this little dance each time I want to create a new project and for the life of me, I can't work out why two identical installations of QT make two different default build paths.

        So if anyone has any ideas, that would be appreciated.

        J Offline
        J Offline
        jsulm
        Lifetime Qt Champion
        wrote on 28 Apr 2020, 05:07 last edited by
        #3

        @NickM I don't know why you get different behaviour, but I'm wondering why you put your projects into Qt installation directory?

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        N L 2 Replies Last reply 28 Apr 2020, 08:20
        0
        • J jsulm
          28 Apr 2020, 05:07

          @NickM I don't know why you get different behaviour, but I'm wondering why you put your projects into Qt installation directory?

          N Offline
          N Offline
          NickM
          wrote on 28 Apr 2020, 08:20 last edited by
          #4

          @jsulm No particular reason, and for what it's worth, this problem happens irrespective of this.

          1 Reply Last reply
          0
          • L Offline
            L Offline
            luoluo
            wrote on 4 Jan 2022, 08:59 last edited by
            #5

            I would like to know how you solved this problem,could you tell me ,please?

            1 Reply Last reply
            0
            • J jsulm
              28 Apr 2020, 05:07

              @NickM I don't know why you get different behaviour, but I'm wondering why you put your projects into Qt installation directory?

              L Offline
              L Offline
              luoluo
              wrote on 4 Jan 2022, 09:10 last edited by
              #6

              @jsulm do you know how did the author solve this problem?

              J 1 Reply Last reply 4 Jan 2022, 09:17
              0
              • L luoluo
                4 Jan 2022, 09:10

                @jsulm do you know how did the author solve this problem?

                J Offline
                J Offline
                jsulm
                Lifetime Qt Champion
                wrote on 4 Jan 2022, 09:17 last edited by
                #7

                @luoluo I don't know whether the OP solved this problem.
                I suggest you open your own topic and describe your situation properly.

                https://forum.qt.io/topic/113070/qt-code-of-conduct

                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