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 VS Tools error messages
Forum Updated to NodeBB v4.3 + New Features

Qt VS Tools error messages

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
8 Posts 2 Posters 707 Views 2 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.
  • PerdrixP Offline
    PerdrixP Offline
    Perdrix
    wrote on last edited by
    #1

    When building my project (VS2019) I'm getting:

    1>Remember to call vcvarsall.bat to complete environment setup!
    1>C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe 64 bit, debug executable
    1>Adding Qt5Svg for qsvgicond.dll
    1>Skipping plugin qtvirtualkeyboardplugind.dll due to disabled dependencies (Qt5Qml Qt5Quick).
    1>Skipping plugin qtvirtualkeyboard_hanguld.dll due to disabled dependencies (Qt5Qml Qt5Quick).
    1>Skipping plugin qtvirtualkeyboard_openwnnd.dll due to disabled dependencies (Qt5Qml Qt5Quick).
    1>Skipping plugin qtvirtualkeyboard_pinyind.dll due to disabled dependencies (Qt5Qml Qt5Quick).
    1>Skipping plugin qtvirtualkeyboard_tcimed.dll due to disabled dependencies (Qt5Qml Qt5Quick).
    1>Skipping plugin qtvirtualkeyboard_thaid.dll due to disabled dependencies (Qt5Qml Qt5Quick).
    1>Direct dependencies: Qt5Core Qt5Gui Qt5Widgets
    1>All dependencies   : Qt5Core Qt5Gui Qt5Widgets
    1>To be deployed     : Qt5Core Qt5Gui Qt5Svg Qt5Widgets
    1>EXEC : warning : Cannot find Visual Studio installation directory, VCINSTALLDIR is not set.
    

    Is there something that I need to do that I haven't done?

    Thanks
    D.

    1 Reply Last reply
    0
    • mrjjM Offline
      mrjjM Offline
      mrjj
      Lifetime Qt Champion
      wrote on last edited by
      #2

      hi
      well did you call vcvarsall.bat ?

      1 Reply Last reply
      0
      • PerdrixP Offline
        PerdrixP Offline
        Perdrix
        wrote on last edited by Perdrix
        #3

        Where/when should that call be made? I'm using VS Tools with the VS2019 GUI. Is there a config option I need to set? IFAIK, vcvars32/vcvars64/vcvarsall are only used from the command line, not the VS2019 GUI.

        mrjjM 1 Reply Last reply
        0
        • PerdrixP Perdrix

          Where/when should that call be made? I'm using VS Tools with the VS2019 GUI. Is there a config option I need to set? IFAIK, vcvars32/vcvars64/vcvarsall are only used from the command line, not the VS2019 GUI.

          mrjjM Offline
          mrjjM Offline
          mrjj
          Lifetime Qt Champion
          wrote on last edited by mrjj
          #4

          @Perdrix
          Oh I though it was from cmdline.

          Try with a clean default project and see if that runs as then we know if
          its due to the actual project or something in the setup is not correct.

          It does seems to compile the exe so can it run after ?

          1 Reply Last reply
          0
          • PerdrixP Offline
            PerdrixP Offline
            Perdrix
            wrote on last edited by
            #5

            59b23a1a-8f8b-41aa-8602-88d481769c6b-image.png

            Looking at the defined macros in VS, VCInstallDir would definitely seem to be set ...

            1 Reply Last reply
            0
            • PerdrixP Offline
              PerdrixP Offline
              Perdrix
              wrote on last edited by Perdrix
              #6

              The problem is happening in the "post-Build" stage where this is invoked:

              call $(QtToolsPath)\qtenv2.bat
              $(QtToolsPath)\windeployqt --pdb --debug $(TargetPath)

              VCInstallDir macro IS set.

              mrjjM 1 Reply Last reply
              0
              • PerdrixP Perdrix

                The problem is happening in the "post-Build" stage where this is invoked:

                call $(QtToolsPath)\qtenv2.bat
                $(QtToolsPath)\windeployqt --pdb --debug $(TargetPath)

                VCInstallDir macro IS set.

                mrjjM Offline
                mrjjM Offline
                mrjj
                Lifetime Qt Champion
                wrote on last edited by
                #7

                @Perdrix
                yes I was kind of suspecting that.

                You can try adding a call for
                vcvarsall.bat

                like the one for qtenv2.bat

                and see.

                I know it seems like VCInstallDir is set but the warning it gives kinda suggest, it doesn't see it.

                1 Reply Last reply
                0
                • PerdrixP Offline
                  PerdrixP Offline
                  Perdrix
                  wrote on last edited by
                  #8

                  I changed the Post-Build step to do this for Release Build:

                  call $(QtToolsPath)\qtenv2.bat
                  call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat"
                  $(QtToolsPath)\windeployqt $(TargetPath)

                  and this for Debug Build:

                  call $(QtToolsPath)\qtenv2.bat
                  call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat"
                  $(QtToolsPath)\windeployqt --pdb --debug $(TargetPath)

                  which appears to have silenced the complaints.

                  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