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 4.7.2 update problems
Forum Updated to NodeBB v4.3 + New Features

Qt Creator 4.7.2 update problems

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
25 Posts 5 Posters 11.3k 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.
  • aha_1980A aha_1980

    @MartinD Please check the Run Environment (Project > Build & Run > Run > Run Settings > Run Environment - especially PATH. I'm pretty sure it's related to something there.

    M Offline
    M Offline
    MartinD
    wrote on last edited by MartinD
    #21

    @aha_1980 Thanks for that point. I found that old Qt Creator adds multiple x64 paths to PATH (my app is 32 bit), e.g.:

    C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64
    C:\Program Files (x86)\Windows Kits\8.1\bin\x64
    C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\

    Whereas new Qt Creator has:
    C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools
    C:\Program Files (x86)\Windows Kits\8.1\bin\x86
    C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\

    Otherwise, the PATH is same. Changing the PATH in new Qt Creator to what old Qt Creator uses has no effect.

    M 1 Reply Last reply
    0
    • M MartinD

      @aha_1980 Thanks for that point. I found that old Qt Creator adds multiple x64 paths to PATH (my app is 32 bit), e.g.:

      C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64
      C:\Program Files (x86)\Windows Kits\8.1\bin\x64
      C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\

      Whereas new Qt Creator has:
      C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools
      C:\Program Files (x86)\Windows Kits\8.1\bin\x86
      C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\

      Otherwise, the PATH is same. Changing the PATH in new Qt Creator to what old Qt Creator uses has no effect.

      M Offline
      M Offline
      MartinD
      wrote on last edited by
      #22

      I intentionally corrupted PATH variable in my Run Settings in new Qt Qreator for project that I'm able to launch and there is in application output:

      10:36:14: The program has unexpectedly finished.
      10:36:14: The process was ended forcefully.

      I.e. different error message from what I get:

      16:55:48: Failed to start program. Path or permissions wrong?
      16:55:48: D:/MyProject/debug/MyAppexited with code -1

      It seems that PATH is set correctly.

      1 Reply Last reply
      0
      • V Offline
        V Offline
        VTiTux
        wrote on last edited by
        #23

        I have the same message error with a new created project (QtCreator v4.9.2)
        ("...exited with code -1 \n The process failed to start. Either the invoked program ... is missing, or you may have insufficient permissions to invoke the program.")
        I compared the run config with my others olders projects, and finaly I unchecked the "run in terminal".
        Now, I'm able to run my project with QtCreator.

        1 Reply Last reply
        0
        • Mariana MeirelesM Offline
          Mariana MeirelesM Offline
          Mariana Meireles
          wrote on last edited by
          #24

          I had the same problem in a Linux and the root of the problem for me was a misconfiguration in the Kit (it was preventing me to choose a device, in my case it was impossible to change the options and I had to create a new one):
          To fix this:

          1. Open QtCreator
          2. Go to the Projects tab
          3. Remove or disable your currently Build & Run kit
          4. Add a new one, make sure your configurations are correct, your debuggers, compilers and Qt version paths are pointing in the right direction.
          5. Enable this new kit for your project
          aha_1980A 1 Reply Last reply
          1
          • Mariana MeirelesM Mariana Meireles

            I had the same problem in a Linux and the root of the problem for me was a misconfiguration in the Kit (it was preventing me to choose a device, in my case it was impossible to change the options and I had to create a new one):
            To fix this:

            1. Open QtCreator
            2. Go to the Projects tab
            3. Remove or disable your currently Build & Run kit
            4. Add a new one, make sure your configurations are correct, your debuggers, compilers and Qt version paths are pointing in the right direction.
            5. Enable this new kit for your project
            aha_1980A Offline
            aha_1980A Offline
            aha_1980
            Lifetime Qt Champion
            wrote on last edited by
            #25

            @Mariana-Meireles yeah, such things sometimes happen after Creator updates. The sledgehammer solution is to quit Creator, delete the .pro.user and the build directories, and the restart Creator.

            But your solution should work too.

            Regards

            Qt has to stay free or it will die.

            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