Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENHANCEMENT] Qt6 support #422

Open
bgermann opened this issue Jan 7, 2023 · 5 comments
Open

[ENHANCEMENT] Qt6 support #422

bgermann opened this issue Jan 7, 2023 · 5 comments

Comments

@bgermann
Copy link

bgermann commented Jan 7, 2023

In May, Qt5 support without payed subsription ends.
Is there a chance to port Bibletime to Qt6 and if so, are there any blockers?

@gholmlund
Copy link
Contributor

I don't believe anyone has tried Qt 6 yet. I doubt there are any blockers.
I think we would only change the master branch so it could be part of a 3.1 release
We could try to be compatible with both Qt 6.4 and 5.15 as long as it does not add much complexity.

I could work on it unless you want to @jaakristioja

@jaakristioja
Copy link
Member

You can, but I don't think this is urgent. Most Linux distributions don't even package Qt6 right now. Because many packages still require Qt5, distributions will most likely continue to provide Qt5 support for at least a few more years. Afaik even KDE is only halfway ported to Qt6.

@jaakristioja
Copy link
Member

jaakristioja commented Sep 29, 2023

As of 30a38d7 I got a BibleTime built against Qt 6.5.3 to start up without crashing. But there is a huge amount of Qt5 -> Qt6 porting work still to be done.

@jaakristioja
Copy link
Member

As of 6c26004 I've removed in builds against Qt6 all uses of Qt functions marked as deprecated in Qt 6.5 and older.

@jaakristioja
Copy link
Member

As of ad8506b building BibleTime against Qt6 no longer depends on the Core5Compat module.

@jaakristioja jaakristioja added this to the 3.1.0 milestone Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants