On Thursday 31 October 2013, Stephen Kelly wrote: > Alexander Neundorf wrote: > > find_package(KF5 ... COMPONENTS karchive solid kcompletion) > > > > call in their CMakeLists.txt and get the same results. > > And if this works for tier3 libs, why not just do the same in tier2 and > > also in tier1... > > Because tier1 doesn't depend on or find KF5 at all, by definition.
Yes, that's what the definition says. Because it was not acceptable according to that definition to have a package KDECMakeStuff, which all tier1 packages would have depended on, the files KDEInstallDirs.cmake, KDECMakeSettings.cmake and KDECompilerSettings.cmake ended up in extra-cmake-modules. IOW, those three files exist only for KF5, and no other reason. Without KF5, they wouldn't be in extra-cmake-modules (that's why they are in a separate directory). IMO, in that sense, those three files are part of KF5, logically. They simply are not a separate package because it was not allowed (by the definition) to have an official tier0 package. See, if tier1 does not depend on anything else KDE specific, remove those three files from e-c-m and see how it goes. Alex _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
