I’m not entirely sure. In principle, you shouldn’t need to set the other variables, since it should find Qt6 from your CMAKE_PREFIX_PATH.
The error message seems more about finding a working compiler.
Is this from the Visual Studio console - that sets up the compiler paths, etc.?
When I had previously gotten Av2 to compile I had to set all three of the variables that I did to get it to work. Not really sure why to be honest.
That’s what I was thinking, although I can’t figure out why it can’t find a working compiler since the Qt5 runs had zero problem with this.
I’m running this direct from my command prompt, not in VS at all. If I try to run using the Cmake GUI, I can see that CMAKE_CXX_COMPILER is set to a path where there most certainly is a working compiler, in fact it is the same exact path that is used for Qt5 compilation.
On the off-chance anyone else is following this…
A significant milestone has been reached: the Linux version of Avogadro is now built against Qt6!
Windows and Mac require further changes to the packaging process which means that migration on those platforms has been postponed until after the upcoming 1.100 release.
This means though that, from 1.100 onwards, the AppImage and Flatpak will be on Qt6, and the versions available from Linux distro’s repositories likely will be too. The nightly AppImage and beta Flatpak are already.
I’ve mentioned the topic a lot on here in the past year, and maybe some would ask why the average user should care about what framework we are using?
Well, while this is mostly a behind-the-scenes change, it does fix various bugs due to them having been fixed in Qt itself or due to Avogadro working better with more modern OSes. To name a couple that are frequently encountered in Avogadro there’s this SSL issue and this bug in plugin dialogs.
Having Avogadro stand on an up-to-date platform will also provide some mod cons such as a more native look on Windows 11 and support for dark mode on Windows, and opens the doors to some nice things for the future, such as universal macOS builds and possibly builds for Windows on ARM.
And to be clear, this included a bunch of hard work, first by @mhanwell and then @matterhorn103