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

Qt Creator 4.7.2 update problems

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

    No, they also don't have .exe suffix in new Qt Creator.

    In old Qt Creator application output when launching starts with:

    Starting D:\Projects\build-MyProject-Desktop_Qt_5_7_0_MSVC2013_32bit-Debug\MyApp\debug\MyApp.exe...

    Whereas in new Qt Creator, as I have already written, there is no .exe suffix. Is this the issue? However, I still don't understand how it is possible that two projects can run and one not.

    aha_1980A Offline
    aha_1980A Offline
    aha_1980
    Lifetime Qt Champion
    wrote on last edited by
    #15

    @MartinD said in Qt Creator 4.7.2 update problems:

    However, I still don't understand how it is possible that two projects can run and one not.

    It could still be that the program crashes because it cannot load a dependent library. Have you checked if you can start the app outside Creator?

    Qt has to stay free or it will die.

    1 Reply Last reply
    0
    • M Offline
      M Offline
      MartinD
      wrote on last edited by
      #16

      Yes, the app can run outside Qt Creator. Also, Qt Creator 4.0.3 can launch this app. Only new Qt Creator 4.7.2 can't launch it.

      aha_1980A 1 Reply Last reply
      0
      • M MartinD

        Yes, the app can run outside Qt Creator. Also, Qt Creator 4.0.3 can launch this app. Only new Qt Creator 4.7.2 can't launch it.

        aha_1980A Offline
        aha_1980A Offline
        aha_1980
        Lifetime Qt Champion
        wrote on last edited by
        #17

        @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.

        Qt has to stay free or it will die.

        M 1 Reply Last reply
        0
        • M MartinD

          It is not the same:
          Executable is "D:\Projects\build-MyProject-Qt_5_7_0_MSVC2013_32bit-Debug\MyApp\debug\MyApp"
          Working dir is "D:\Projects\build-MyProject-Qt_5_7_0_MSVC2013_32bit-Debug\MyApp"

          I also tried to minimize my problematic executable project by compiling only empty main function. The executable now links only to some system dlls. Still the same issue.

          jsulmJ Offline
          jsulmJ Offline
          jsulm
          Lifetime Qt Champion
          wrote on last edited by jsulm
          #18

          @MartinD said in Qt Creator 4.7.2 update problems:

          Executable is "D:\Projects\build-MyProject-Qt_5_7_0_MSVC2013_32bit-Debug\MyApp\debug\MyApp"
          Working dir is "D:\Projects\build-MyProject-Qt_5_7_0_MSVC2013_32bit-Debug\MyApp"

          Try to change the working directory to "D:\Projects\build-MyProject-Qt_5_7_0_MSVC2013_32bit-Debug\MyApp\debug"

          And compare these settings with QtCreator 4.0.3

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

          1 Reply Last reply
          0
          • M Offline
            M Offline
            MartinD
            wrote on last edited by MartinD
            #19

            Already tried setting working directory to that.

            The difference is, that in Qt Creator 4.0.3 the Executable has .exe suffix, there is D:\Projects\build-MyProject-Qt_5_7_0_MSVC2013_32bit-Debug\MyApp\debug\MyApp.exe

            jsulmJ 1 Reply Last reply
            0
            • M MartinD

              Already tried setting working directory to that.

              The difference is, that in Qt Creator 4.0.3 the Executable has .exe suffix, there is D:\Projects\build-MyProject-Qt_5_7_0_MSVC2013_32bit-Debug\MyApp\debug\MyApp.exe

              jsulmJ Offline
              jsulmJ Offline
              jsulm
              Lifetime Qt Champion
              wrote on last edited by
              #20

              @MartinD Well, in my QtCreator there is no .exe suffix as well and the app starts from QtCreator. Must be something else. As @aha_1980 said it is most probably something in Run settings - you can compare those too between both QtCreator versions.

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

              1 Reply Last reply
              0
              • 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