Qt 6.0 development and qelectrotech (Page 7 of 7)

French :
Bonjour, durant mes vacances j'ai testé sur une nouvelle branche basé sur le master (avec des mélanges de commit provenant de la branche qt6 cmake) la bascule avec qt6 et kf6. Tout n'est pas encore fini mais ça avance bien. Par contre je n'ai aucun problème avec les bibliothèques KF6. Pourquoi avoir supprimé kautosavefile ainsi que kwidgetaddon, pour les réimplementé nous même ? Je n'en vois pas l'intérêt, je préfère largement garder du code provenant de KF6 qui est grandement corrigé et testé que de réinventer la roue. Ai je raté quelque-chose ?

Translated english
Résultat de la traduction

Hello, during my vacation I tested switching to qt6 and kf6 on a new branch based on the master (with a mix of commits from the qt6 cmake branch). It's not quite finished yet, but it's coming along nicely. However, I have no problems with the KF6 libraries. Why remove kautosavefile and kwidgetaddon, only to reimplement them ourselves? I don't see the point. I would much rather keep code from KF6, which has been extensively corrected and tested, than reinvent the wheel. Have I missed something?

Hi Joshua,

As a whole I agreed, the KF6 libraries are pretty well tested and if they can be used instead of re-implementing them it makes sense. Why take on the extra work and possibly introduce bugs, if it's not necessary.

My main question here comes down to Windows. As I understand it KF6 can build on Windows, but I haven't succeeded yet. I was trying to get QET building on my Windows based work machine to see what I could do to help with the Qt 6 progress. The sticking point was KF6, the Windows build instructions that have been mentioned in the forum use vcpkg. Vcpkg only has KF5, and I found some issues and forum posts, it doesn't look like KF6 is coming to vcpkg any time soon. I started looking into getting KDE Craft set up so I could compile KF6 on Windows and maybe getting it working with a Qt6 version of QET, but didn't get it working before I went on vacation (I didn't bring my Windows based work laptop with me, and I won't be back for another few days).

If I recall correctly Laurent said somewhere in the forums that the official Windows release is cross-compiled from Linux. If that is the case, and it's working fine with Qt6 and KF6, than perhaps getting QET and KF6 building directly on Windows isn't that big of a deal, although I think it would be nice to actually be able to build the program on Windows itself.

Have you tested your branch on Windows, or tested cross-compiling it?
Is this branch publicly available if I wanted to try and do some testing on it?

It's sad that elevatormind is no longer participating here!
He contributed several pull requests for eliminating KF5/KF6 and introduced a number of changes to QETs code to compile/work under Qt6, which he also explained and described here in the forum.