On Friday 04 of March 2016 18:43:34 Martin Koller wrote:
On Friday 04 March 2016 07:36:44 Luca Beltrame wrote:
kolourpaint needs libqimageblitz, where also a package libqimageblitz5-devel
I don't recall if qimageblitz had ever a Qt5 release. This is another problem.
I checked out the sources from SVN and simply built it with Qt5. The cmake file in the repo already handles Qt5. There's even the possibility to build it either against Qt4 or Qt5: option(QT4_BUILD "Force building with Qt4 even if Qt5 is found")
How can we go about this ? How do distributors handle this case, when a lib can be built either with Qt4 or with Qt5 ? Or do they build both and install the headers in different subdirs ? How would then a cmake file (e.g. from kolourpaint) find it ? Or is it only one or the other (like ksane did it) ? If the latter, what must be done (from my side) to notify distributors that they need to build it with Qt5 so that a KF5 based kolourpaint can be built ? And would a move to Qt5 only not lead to troubles for other projects using the Qt4 version of the lib ?
Ideally it should be done similar to libdbusmenu e.g. http://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu-qt/trunk/view/head:/C... So Qt4 apps/libs needing imageblitz can keep the old version (w/o conflicts) and Qt5 ones just need newer version. This also means it's not needed to keep Qt4 compat, but both libname (not just soversion) and header paths/cmake files, etc. should be different from each other. One more step - the adjusted code needs a release :D Cheers, Hrvoje -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org