Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Can not build application msvc2017, Qt 5.10.1, Qt creator 4.8.1
Forum Updated to NodeBB v4.3 + New Features

Can not build application msvc2017, Qt 5.10.1, Qt creator 4.8.1

Scheduled Pinned Locked Moved Solved General and Desktop
17 Posts 4 Posters 4.9k 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.
  • U Umbaman

    Do I need to run vcvars manually?

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

    @Umbaman

    No, Creator runs it for you. But you can check if you can open a Visual Studio command prompt from the Start Menu. That should exec the same batch file and set up the environment.

    Does that work without problems?

    Qt has to stay free or it will die.

    U 1 Reply Last reply
    1
    • aha_1980A aha_1980

      @Umbaman

      No, Creator runs it for you. But you can check if you can open a Visual Studio command prompt from the Start Menu. That should exec the same batch file and set up the environment.

      Does that work without problems?

      U Offline
      U Offline
      Umbaman
      wrote on last edited by
      #9

      @aha_1980
      Yes It does.!

      1 Reply Last reply
      0
      • J Offline
        J Offline
        Jerry.Wilson
        wrote on last edited by
        #10

        After line 3 the qmake exited normally, it start the qmake again with "-f" param, I think it should be jom.exe not qmake.exe, qmake has no option "-f", did you change it?

        U 1 Reply Last reply
        2
        • J Jerry.Wilson

          After line 3 the qmake exited normally, it start the qmake again with "-f" param, I think it should be jom.exe not qmake.exe, qmake has no option "-f", did you change it?

          U Offline
          U Offline
          Umbaman
          wrote on last edited by
          #11

          @Jerry.Wilson
          No I didn't! I don't even know how. I wanted to remove the -f option

          J 1 Reply Last reply
          0
          • U Umbaman

            @Jerry.Wilson
            No I didn't! I don't even know how. I wanted to remove the -f option

            J Offline
            J Offline
            Jerry.Wilson
            wrote on last edited by
            #12

            @Umbaman
            Mmm...as I saw in your picture, you choose qmake.exe as your make tool in the Make Path, I think that is the reason. Qmake is not a make tool, use jom.exe and try again.

            U 1 Reply Last reply
            3
            • J Jerry.Wilson

              @Umbaman
              Mmm...as I saw in your picture, you choose qmake.exe as your make tool in the Make Path, I think that is the reason. Qmake is not a make tool, use jom.exe and try again.

              U Offline
              U Offline
              Umbaman
              wrote on last edited by Umbaman
              #13

              @Jerry.Wilson hmmm. Something seems to be happening.

              This is what I am getting now

              C:\Qt\5.10.1\msvc2017_64\include\QtCore/qglobal.h(45): fatal error C1083: Cannot open include file: 'type_traits': No such file or directory
              

              Edit:
              this guy here (https://nnarain.github.io/2017/11/10/Config-issues-with-Qt-and-Visual-Studio.html) nailed it!
              The corresponding registry key was pointing to the community edition I had, before installing visual studio professional.

              I can see a few compilers now autodetected, but not a single kit autoconfigured...
              Manually setting a compiler seems to be working but I cannot compile my project correctly.

              Example Output

              :-1: error: LNK1181: cannot open input file 'debug\main.obj'

              aha_1980A 1 Reply Last reply
              0
              • U Umbaman

                @Jerry.Wilson hmmm. Something seems to be happening.

                This is what I am getting now

                C:\Qt\5.10.1\msvc2017_64\include\QtCore/qglobal.h(45): fatal error C1083: Cannot open include file: 'type_traits': No such file or directory
                

                Edit:
                this guy here (https://nnarain.github.io/2017/11/10/Config-issues-with-Qt-and-Visual-Studio.html) nailed it!
                The corresponding registry key was pointing to the community edition I had, before installing visual studio professional.

                I can see a few compilers now autodetected, but not a single kit autoconfigured...
                Manually setting a compiler seems to be working but I cannot compile my project correctly.

                Example Output

                :-1: error: LNK1181: cannot open input file 'debug\main.obj'

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

                @Umbaman,

                good, it seems we get forward :)

                • Can you show your compilers and kits screens again now?
                • Can you check if a newly created project compiles?
                • If not, please post the complete compile output.

                Regards

                Qt has to stay free or it will die.

                1 Reply Last reply
                2
                • U Offline
                  U Offline
                  Umbaman
                  wrote on last edited by
                  #15
                  1. Compilers

                  0_1550151994648_newCompilers.JPG

                  Kits
                  0_1550151918677_new Kits.JPG

                  1. A new project compiles, runs and can be debugged successfully using the Desktop Kit. I was getting the error mentioned due to white spaces in my path.

                  As for the UWP kit I get the following output

                  :-1: warning: winrt_manifest_install.path is not defined: install target not created
                  

                  therefore nothing happens when I run the project.

                  aha_1980A 1 Reply Last reply
                  0
                  • U Umbaman
                    1. Compilers

                    0_1550151994648_newCompilers.JPG

                    Kits
                    0_1550151918677_new Kits.JPG

                    1. A new project compiles, runs and can be debugged successfully using the Desktop Kit. I was getting the error mentioned due to white spaces in my path.

                    As for the UWP kit I get the following output

                    :-1: warning: winrt_manifest_install.path is not defined: install target not created
                    

                    therefore nothing happens when I run the project.

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

                    @Umbaman

                    Do you need UWP/WinRT? I'm out here, I have never used it...

                    Qt has to stay free or it will die.

                    1 Reply Last reply
                    1
                    • U Offline
                      U Offline
                      Umbaman
                      wrote on last edited by
                      #17

                      Yes I do.
                      I need to develop apps for Windows 10 IoT.

                      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