Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

UWP fails to Publish as a Qt/MSBuild project



  • I'm using Qt 5.15.2 and VS add-in 2.6.0.7. I can build and run a Qt/MSBuild project; however, I can not publish it to a UWP package. I had to create the project by starting off with QtCreator project because of a bug in qmake. I created the intitial project with the following command, qmake -tp vs. I then converted the project to a Qt/MSBuild project with the VS Add-in. When I publish the project I get the following error:

    1>Target _SplitResourcesPri:
    1> Building target "_SplitResourcesPri" completely.
    1> Output file "release\split.generatedFiles.txt" does not exist.
    1> Using "GenerateProjectPriFile" task from assembly "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.Build.Packaging.Pri.Tasks.dll".
    1> Task "GenerateProjectPriFile"
    1> C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(4176,5): error MSB4044: The "GenerateProjectPriFile" task was not given a value for the required parameter "MakePriExeFullPath".
    1> Done executing task "GenerateProjectPriFile" -- FAILED.
    1>Done building target "_SplitResourcesPri" in project "DataStreamer.vcxproj" -- FAILED.
    1>
    1>Done building project "DataStreamer.vcxproj" -- FAILED.
    1>
    1>Build FAILED.
    1>
    1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(4176,5): error MSB4044: The "GenerateProjectPriFile" task was not given a value for the required parameter "MakePriExeFullPath".
    1> 0 Warning(s)
    1> 1 Error(s)
    1>
    1>Time Elapsed 00:00:00.68
    ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
    ========== Package: 0 succeeded, 1 failed ===========

    Does anyone have any idea how to fix this issue?



  • I have the same problem (same Qt Version and same Qt VS tool) , did you solve the problem ?


Log in to reply