[DiapDealer]

I'm in no hurry at all to join Qt in its quest to make only the very latest hardware (and the very latest OSes running on it) the only viable options for both users and developers.

As such, I'll work at my leisure (in a very piecemeal manner) to modify Sigil's codebase (and build system) to support building with both Qt5/Qt6. When Sigil CAN be built using Q6, I'll invite hobbyists to experiment with those Qt6 Sigil builds to assist in working out most bugs.

But make no mistake: I probably won't start distributing any Sigil Qt6 installers (or recommending package maintainers do) until such time as NOT moving to Qt6 might begin harming Sigil's ability to stay relevant.

It will be a long, long rollout (and as KevinH mentioned, Qt5.15 will come before) before Sigil is able to built using Qt6, let alone be distributed with Qt6. We'll also need to give plugin devs a lot of lead time to make sure their PyQt5-based plugins will be able to work with both Qt5 and Qt6 versions of Sigil.

It won't be impossible at all. But just the changes necessary to get Sigil to compile using Qt6 will be extensive and invasive (and that's WITH Qt's compatibility libraries intended to facilitate such porting). Getting the cmake build system (and the codebase) to support using either Qt5 or Qt6 will be more daunting, but necessary, I think, to continue to support older systems that Qt6 will leave behind.

A C++17-compatible compiler is required to build Qt6 applications.