On Saturday 27 December 2014 12:24:25 Harald Sitter wrote: > I think(tm) the way to fix this properly (which I have not ever seen > done by us :P) is fiddling with the find_package related variables > (supposedly PACKAGE_VERSION_COMPATIBLE would be used) to indicate that > a given candidate package is not compatible for what was looked for. > This combined with the way find_package finds its cmake config > (globbing), by the way should allows for easy installation > compatibility even in the simplest of libraries. > > i.e. > > - cmake/libfoo1/FooConfig.cmake > checks PACKAGE_FIND_VERSION -> sets PACKAGE_VERSION_COMPATIBLE=false > if not something like 1.* > > - cmake/libfoo2/FooConfig.cmake > as libfoo2 but makes sure the looked for version is 2.* > > - headers get installed to a soname'd dir (which we kind of have for > KF5 at large but not individual libs)
Yes, this is exactly what the *ConfigVersion.cmake file is supposed to do. WRITE_BASIC_PACKAGE_VERSION_FILE()[0], which we use to write those files, even has a "COMPATIBILITY SameMajorVersion" option, which should be used by those projects for which that makes sense. Alex [0]: http://www.cmake.org/cmake/help/v2.8.12/cmake.html#module:CMakePackageConfigHelpers _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
