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

chat: require Qt 6.8 and fix #includes #3498

Merged
merged 2 commits into from
Feb 18, 2025
Merged

Conversation

cebtenzzre
Copy link
Member

@cebtenzzre cebtenzzre commented Feb 14, 2025

The theme of this PR is code simplification and preventative maintenance related to Qt updates.

Users have reported build failures on versions of Qt prior to 6.8. We only ever build against Qt 6.8 and newer, so let's require that explicitly. Otherwise, we would have to put effort towards actually supporting older Qt, which is not worth our time. This allows us to simplify server.cpp, which had some code that only applied to older Qt.

Additionally, fix the #includes based on this Qt version. One of the more notable changes since Qt 6.4 was the split of the <QtGlobal> header (and we no longer support Qt 6.4). But a pass with IWYU shows that there were less cosmetic issues as well. The goal of this change is to be robust to Qt updates by relying only on names documented to be declared in a given header.

Signed-off-by: Jared Van Bortel <[email protected]>
Signed-off-by: Jared Van Bortel <[email protected]>
@cebtenzzre cebtenzzre force-pushed the update-qt68-fix-includes branch from 56cc05e to 0e10f6c Compare February 18, 2025 16:33
@cebtenzzre
Copy link
Member Author

The CI build passed on all platforms (packaging hasn't finished yet on Windows amd64 but that's irrelevant).

@cebtenzzre cebtenzzre requested a review from manyoso February 18, 2025 17:06
@cebtenzzre cebtenzzre merged commit 29f2977 into main Feb 18, 2025
9 of 16 checks passed
@cebtenzzre cebtenzzre deleted the update-qt68-fix-includes branch February 18, 2025 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants