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

Some preparations for KDE6/QT6 #240

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Some preparations for KDE6/QT6 #240

wants to merge 8 commits into from

Conversation

t-8ch
Copy link
Contributor

@t-8ch t-8ch commented Aug 18, 2024

These are some cleanups I encountered when trying to build for KDE6/QT6.
Most of them are already applicable today.

Feel free to pick up single commits now, or incorporate them into your migration work.

@dragotin
Copy link
Owner

Thanks a lot, that is very appreciated.

FYI, my plan is as follows: I am currently working on the (already way to big) branch newshared for Kraft 2.0 as described in the discussion. Once that is mergeable, it will be merged to master. Than, the port to Qt6 can happen on master easily.

The stable 1.x version will be maintained in a branch after that.

@dragotin
Copy link
Owner

Would you mind rebasing this one to see if the actions run through? Thanks!

The old names have been deprecated in KDE5 and are removed in KDE6.
The definitions are already propagated as necessary by the targets.
There is no need to duplicate them.
This variable is a leftover from QT4, it is not set anymore.
The same logic is already part of the corresponding header file.
The CMake targets already set up the include path properly.
Use them instead of adding custom global include directories.
These global include directories are nearly unused.
Replace them with a dedicated include directory for the single user.
@t-8ch
Copy link
Contributor Author

t-8ch commented Sep 27, 2024

It didn't work. But it should be fixable in a reasonable manner.

CMake can automatically compile resources when added to a targets
sources. This avoids a call to a qt5 specific API which would not work
on qt6.

Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
@t-8ch
Copy link
Contributor Author

t-8ch commented Sep 28, 2024

That seems to have worked. I dropped the breaking commit, and will see what is the issue.

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