Uploaded image for project: 'Qt Visual Studio Tools'
  1. Qt Visual Studio Tools
  2. QTVSADDINBUG-819

Qt_INCLUDEPATH_ not defined

    XMLWordPrintable

Details

    • Windows
    • 04e03065203550fdc2a06070d5250f66cbff7d4b

    Description

      I'm using VS2019 with plugin version 2.5.2.1.  When creating a new project for UWP,  Qt_INCLUDEPATH_ is not defined.   This causes errors because the included headers cannot be found and it generates a qmake error. 

       

      I used the Qt Widgets application template to generate the UWP project files.  After the wizard finishes, I see the following in the Qt VS Tools output window.

      == Qt Visual Studio Tools version 2.5.2 (rev.1)
Initialized in: 530.18 msecs
 Main (UI) thread: 125.82 msecs
QtWidgetsApplication1.vcxproj: background build FAILED!
QtWidgetsApplication1.vcxproj: background build FAILED!
QtWidgetsApplication1.vcxproj: background build FAILED!

       

      The output for the Deployment output window.

       DeviceConfiguration/GetDevices DeviceConfiguration/GetDevices Caller = <GetEmulatorsAsync>d__7ConfigurationParser/Constructor: STARTConfigurationParser/Constructor/EnumeratePackages: STARTReading tools configuration from Visual Studio installation at 'c:\program files (x86)\microsoft visual studio\2019\professional\common7\ide\commonextensions\microsoft\tailoredprojectservices'. GlobalConfigurationFolderPresent = True NumberOfPackagesFound = 22 ConfigurationParser/Constructor/EnumeratePackages/Package Id = f8ce90e1-19bc-472a-b625-9c081fac46df Name = VSGraphics Debugging Package DUIC Architectures = Arm|X86|X64 VisualStudioPackage = False ConfigurationParser/Constructor/EnumeratePackages/Package Id = 44eeed0d-971c-4546-bc24-b6a5cbfae959 Name = GPU Collector Agent Architectures = Arm|X86|X64 VisualStudioPackage = False ConfigurationParser/Constructor/EnumeratePackages/Package Id = 8e61b271-9853-41c9-b845-4d32865c306f Name = App Analysis Collection Agent Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = e0999a8f-0200-4738-ae1e-b45742be6b6b Name = CoreCLR Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = efb65f05-52ca-49fe-9799-0d120b3e8c40 Name = Memory Profiler Collection Agent Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = c99f0de0-95fe-4c64-9d17-efa7574c358b Name = Memory Profiler v2 Collection Agent Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = bff8ef71-b423-4e11-8f4b-9ce1061615a2 Name = Native Memory Profiler Win10 Collection Agent Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = eb22551a-7f66-465f-b53f-e5aba0c0574e Name = msvsmon native Package Architectures = Arm|X86|X64|Arm64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 62b807e2-6539-46fb-8d67-a73dc9499940 Name = msvsmon managed Package Architectures = Arm|X86|X64|Arm64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = d8b19935-bdbf-4d5b-9619-a6693afd4554 Name = msvsmon script Package Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 322e47a7-c871-4db0-b663-2b836b9a6427 Name = Diagnostics Hub Standard Collector (Post-mortem) Architectures = Arm|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = f4461251-3ffb-4108-9743-364bb931faf2 Name = Diagnostics Hub Standard Collector Service Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 98e13d7b-2ac3-4b11-bbeb-758ad8bd607a Name = Diagnostics Hub Collector Bridge Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 96f1f3e8-f762-4cd2-8ed9-68ec25c2c722 Name = CPU Usage Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 87c20e3c-a84e-4f56-8bcb-a09a23bfe077 Name = DotNetAlloc Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 4ec3701d-0b28-4ae9-8bc4-20e88ce94c81 Name = EventsViewer Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = f1498e2f-1808-4e2a-8c86-b888a59d8446 Name = Database Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = db99fe6f-5272-4638-bf5c-c32fc1527b26 Name = DotNetAsync Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = cc6587b3-a749-4158-989f-1c3bb2b234f5 Name = Windows10RemoteTools Architectures = Arm|Arm64|X64|X86 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 9093ee4a-01e5-44ed-9214-0b4d15023fde Name = XAML UI Debugger package Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = b968cc6a-d2c8-4197-88e3-11662042c291 Name = XAML UI Debugger package Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = True ConfigurationParser/Constructor/EnumeratePackages/Package Id = 57e8cc1f-36e5-41b7-972f-80e4f1016bfc Name = XAML UI Debugger dependency Package Architectures = Arm|Arm64|X86|X64 VisualStudioPackage = FalseConfigurationParser/Constructor/EnumeratePackages: END (Success, 0:00:00.584)ConfigurationParser/Constructor/EnumerateEmulators: START NumberOfDevicesFound = 0ConfigurationParser/Constructor/EnumerateEmulators: END (Success, 0:00:00.06)ConfigurationParser/Constructor: END (Success, 0:00:00.652)IsEmulatorSupported: START Is64BitOperatingSystem = TrueDetectSlat: START isHyperVRunning = False isHardwareVirtualizationSupported = True isHardwareVirtualizationEnabledInBIOS = TrueDetectSlat: END (Success, 0:00:01.252) SlatState = SlatAndHWVEnabled IsEmulatorSupported = TrueIsEmulatorSupported: END (Success, 0:00:01.257)

      Here is the error generated from QMake when I try to build the project.

      1>------ Build started: Project: QtWidgetsApplication1, Configuration: Debug Win32 ------
1>Reading Qt configuration (C:\Qt\5.15.1\winrt_x86_msvc2019\bin\qmake.exe)
1>QtWidgetsApplication1.vcxproj : error : ERROR running qmake
1>QtWidgetsApplication1.vcxproj : error : qmake: (C:\Qt\5.15.1\winrt_x86_msvc2019\bin\qmake.exe)
1>QtWidgetsApplication1.vcxproj : error : qmake: $PWD=C:\Users\sten0\AppData\Local\Temp\th5d45mc.qmv
1>QtWidgetsApplication1.vcxproj : error : qmake: Project ERROR: Failed to find the Visual Studio installation directory.
1>QtWidgetsApplication1.vcxproj : error : qmake: Error creating Makefile
1>QtWidgetsApplication1.vcxproj : error :
1>Done building project "QtWidgetsApplication1.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========

      I have attached the generated qmv folder and the project itself.  If you need more, please let me know.

      Attachments

        For Gerrit Dashboard: QTVSADDINBUG-819
        # Subject Branch Project Status CR V
        318836,3 toolchain.prf: Use vswhere to obtain VS installation path dev qt/qtbase Status: MERGED +2 0
        318936,2 toolchain.prf: Use vswhere to obtain VS installation path 5.15 qt/qtbase Status: MERGED +2 0

        Activity

          People

            mecfc Miguel Costa
            steno Jon Mullen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes