Guidelins for one codebase that builds with Qt5 and Qt6?

[Thomas Baumgart]

On Dienstag, 6. August 2024 10:56:26 CEST Klaas Freitag wrote:

> Am 06.08.24 um 09:22 schrieb Halla Rempt:
> 
> Hello,
> 
> >> If it's a lot of work and/or manpower is limited (it's always, isn't it?!) it
> >> may be better to do a Qt-6-only port. That's what we're just doing for
> >> KPhotoAlbum.
> > 
> > That's what I tried at first, but it soon became clear that while actual porting is mostly mechanical, making Krita actually work with Qt6 is going to be a long process. We cannot afford to not be able to release Krita again for half a year or longer, so we have to find a way to keep releasing a working Krita while keeping the Qt6 port up to date in the face of huge projects like the text shape refactoring.
> 
> I agree, this is what concerns me with Kraft as well. It's users are 
> also not particularly bleeding edge, so until most distros are shipping 
> and working with KF6 having a maintained KDE 5 version is valuable.

KMyMoney chimes in here as well.

-- 

Regards

Thomas Baumgart

-------------------------------------------------------------
morphir: so much confusion :S kmake, kdemake, qmake make cmake etc.
logixoul: you forgot cmakekde :)
morphir: and bakemeacake
-------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 868 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20240806/0c3aa1de/attachment-0001.sig>