Skip to content

Conversation

@CasparKielwein
Copy link

In the CMakeLists.txt add a branch to check of qt6 is available.
If it is, use that, otherwise assume QT5.

In qfsignalproxy slightly adapt call to constructor of QVariant.
QVariant(type, void*) signature has changed between QT5 and QT6.

change deprecated call to QQmlListProperty(..)

@CasparKielwein
Copy link
Author

I tried to maintain compatibility with the currently supported version by using pre-compiler switches.
I am in no way married to that solution and happy to change supported versions etc.

@OlivierLDff
Copy link
Contributor

Why don't you go with the one line find_package(QT NAMES Qt6 Qt5 COMPONENTS Core REQUIRED)
Like in Qt documentation: https://doc-snapshots.qt.io/qt6-dev/cmake-qt5-and-qt6-compatibility.html#supporting-older-qt-5-versions

In the CMakeLists.txt add a branch to check of qt6 is available.
If it is, use that, otherwise assume QT5.

In qfsignalproxy slightly adapt call to constructor of QVariant.
QVariant(type, void*) signature has changed between QT5 and QT6.

in qfstore adapt call to constructor of QQmlListProperty.
Signature has changed between QT5.13 and QT6
@CasparKielwein
Copy link
Author

Why don't you go with the one line find_package(QT NAMES Qt6 Qt5 COMPONENTS Core REQUIRED)
Like in Qt documentation: https://doc-snapshots.qt.io/qt6-dev/cmake-qt5-and-qt6-compatibility.html#supporting-older-qt-5-versions

I was not aware of this option and changed it.

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