- Update to 1.1.0: * Deprecated Qt4 support * Improvements in Qt5 support * Fix in URL parsing, preventing Double Encoding of URLs
I take Qt5 support is now on by default? (by reading the cmake call)
Yes.
Actually BUILD_WITH_QT4 is now ON by default.
Although, it was already built with/for Qt5 previously if only Qt5 was found. I.e. BUILD_WITH_QT4 was/is only relevant if both Qt4 and Qt5 are found during the build, in which case it built for Qt4 previously and now for Qt5.
Erm, sorry. It's OFF by default now of course.
Relevant upstream change: https://github.com/gpodder/libmygpo-qt/commit/b84549b8803033b803f7d4dc14d5dcd7a5c344b7
For rectification, though not really relevant here: BUILD_WITH_QT4=ON does disable looking for Qt5.
It will fallback to Qt4 if Qt5 is not found though even without it, so BUILD_WITH_QT4=ON would not really be necessary for the Qt4 package...
wolfi323 created request about 6 years ago
luca_b accepted request about 6 years ago
The Open Build Service is an openSUSE project.
I take Qt5 support is now on by default? (by reading the cmake call)
Yes.
Actually BUILD_WITH_QT4 is now ON by default.
Although, it was already built with/for Qt5 previously if only Qt5 was found. I.e. BUILD_WITH_QT4 was/is only relevant if both Qt4 and Qt5 are found during the build, in which case it built for Qt4 previously and now for Qt5.
Erm, sorry. It's OFF by default now of course.
Relevant upstream change: https://github.com/gpodder/libmygpo-qt/commit/b84549b8803033b803f7d4dc14d5dcd7a5c344b7
For rectification, though not really relevant here: BUILD_WITH_QT4=ON does disable looking for Qt5.
It will fallback to Qt4 if Qt5 is not found though even without it, so BUILD_WITH_QT4=ON would not really be necessary for the Qt4 package...