Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Migrating VS 2019 Qt project from VS Project Format v3.2 to v3.4

Migrating VS 2019 Qt project from VS Project Format v3.2 to v3.4

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
1 Posts 1 Posters 167 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.
  • Y Offline
    Y Offline
    Yurky
    wrote on last edited by Yurky
    #1

    I have a Qt v5.13.2 project that builds in VS 2109 v16.9.2 on one machine with WIN 10 v1809,bld17763.2237 but fails in VS 2019 v16.11.1 on another new machine with WIN 10 v20H2,bld19042.1237...

    I noticed that my Qt project uses VS Project Format v3.2 while a newly created Qt widget project uses VS Project Format v3.4 and builds successfully...

    When I copied the project repo to the new machine, opened it in VS 2019, then tried to build I get this error "QtMsBuild: could not locate qt.targets, qt.props; project may not build correctly."

    After investigating online, inspecting and comparing the .proj files for the two projects, I figure somehow my project needs to be ported/migrated from v.32 to v3.4...

    I cannot find any complete step-by-step guidance to do this...any suggestions would be beneficial...

    Edit: On further research I used the Qt VS Tools extension to create a basic .pro/.pri file set for my project on the legacy machine, then copied them over to the new machine, created an empty Qt project, then imported the .pro file, and it required the VS .proj file to be regenerated (optional, but I had to do it to convert to v3.4)...problem is that all my configurations set up in VS 2019 are not migrated and I could not find a simple way to export that complete info from the Property Manager to a file...so I did it manually...

    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