Qt5 and Visual Studion 2022

[d_stranz]

No worries. I am using Qt 5.14.2 built with VS 2015 for development with VS 2022. Since about VS 2015, Microsoft made all binaries compiled with the "Platform toolset" parameter set to "v14x" (where "x" is 0 - 3 currently) compatible with each other. So you can link a v140 binary with a v143 binary and all works fine.

Capture.jpg

I did run into a few glitches. For one, it took hours to build because I did not exclude the examples and there are hundreds of them. It also failed building qtdeclarative (part of QML) because it could not find python. Once I added that to my PATH and reopened the command prompt, that part built. It failed again somewhere further down the line, but all of the major libraries had been built. If I ever do this again for real I will set up a .bat file with an appropriate set of features to build instead of having it build everything. For my desktop app development, I don't use much beyond the core set of functionality.

Edit March 29 2023:

I had to build Qt 5.15 from source because of another project that required that version. I used VS 2022 for the build and followed the steps above. To make it a bit easier, I wrote a little one-line .bat file to start the configuration process:

..\src\configure -opensource -prefix C:\Qt\5_15_3\5.15.3\msvc2022_64 -nomake examples -nomake tests -skip qtwebengine -skip qtconnectivity

..\src\configure -opensource -prefix C:\Qt\5_15_3\5.15.3\msvc2022_64 -nomake examples -nomake tests -skip qtwebengine -skip qtconnectivity

To copy to clipboard, switch view to plain text mode 

After configuring, I started the build in the evening and it was done without errors by the next morning. "nmake install" copied the appropriate files to the "prefix" (install) directory.

When I tried to build the docs (nmake docs) it failed because for some reason dqoc.exe was not built (even though assistant.exe was). So I copied qdoc.exe from my previous Qt5 install into the new install bin directory and all worked fine. There is probably a configure option to fix that.