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. Qt Creator Qt Versions saying "qmake does not exist or is not executable"
Forum Updated to NodeBB v4.3 + New Features

Qt Creator Qt Versions saying "qmake does not exist or is not executable"

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
3 Posts 2 Posters 1.5k 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.
  • H Offline
    H Offline
    hluo
    wrote on last edited by hluo
    #1
    My Qt Creator was 4.15.2 and it worked well. 
    After updating to Qt Creator 7.0.0, it can automatically detect my installed Qt Versions, but says "qmake does not exist or is not executable" to each Qt Versions and labels them as invalid. Further more, the Qt Creator 7.0.0 starts up extremely slow, usually costs more than 5 minutes, opening the Options form in the Tools menu also costs very long time, I guess it may be checking the qmake.exe but gets some problems. I have tried "Link with Qt..." and it had no effects.
    Later I tried Qt Creator 6.0.2, it has the same problems as Qt Creator 7.0.0.
    I tried Qt Creator 5.0.3, it works well as 4.15.2, starts up quickly and detects Qt Versions correctly without invalid label.
    My OS is Windows 10 Pro x64, I have installed VS2010, VS2017, VS2019 and VS2015 build tools, I have installed Qt 5.9.9 msvc2015 32 and Qt 5.14.2 msvc2017 32&64.
    So what may be the cause of these two problems and how to solve them?
    

    Thanks a lot.

    1 Reply Last reply
    1
    • Z Offline
      Z Offline
      ziller
      wrote on last edited by
      #2

      That is strange, have never heard of that before.

      There have been two potentially relevant changes in Qt Creator 6:

      We added a layer to running processes. You can try switching to the old way of starting processes by setting the environment variable QTC_USE_QPROCESS=1 and starting Qt Creator with that.

      We switched to Qt 6. We still provide Qt 5-based snapshots, so maybe you could try if the Qt 5-based build works for you: https://download.qt.io/snapshots/qtcreator_qt5/7.0/7.0.0/111/

      H 1 Reply Last reply
      0
      • Z ziller

        That is strange, have never heard of that before.

        There have been two potentially relevant changes in Qt Creator 6:

        We added a layer to running processes. You can try switching to the old way of starting processes by setting the environment variable QTC_USE_QPROCESS=1 and starting Qt Creator with that.

        We switched to Qt 6. We still provide Qt 5-based snapshots, so maybe you could try if the Qt 5-based build works for you: https://download.qt.io/snapshots/qtcreator_qt5/7.0/7.0.0/111/

        H Offline
        H Offline
        hluo
        wrote on last edited by hluo
        #3

        @ziller Thank you very much.
        I tried to set QTC_USE_QPROCESS=1 and run Qt Creator 7.0.0 in cmd, the problems were solved.
        I tried to use the Qt 5-based build and started it by double clicking the exe, the problems existed.

        I doubt whether it is caused by my PC's safety software. Our company installs self-developed safety software for each PC. I'm not clear about its working strategy and changing its settings is almost forbidden. I guess the adding a layer to running processes way might be effected by the safety software?

        Now I can write a .bat file to start my Qt Creator 7, but may there be any better way to solve the problem once and for all?

        Thank you.

        1 Reply Last reply
        1

        • Login

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