On 13.01.11 08:01:05, Ian Monroe wrote: > On Thu, Jan 13, 2011 at 03:11, Esben Mose Hansen <[email protected]> wrote: > > On Wednesday 12 January 2011 15:28:38 Marcel Wiesweg wrote: > >> a) should CMake modules be moved up to kdelibs or down to the submodule > >> that needs them? > > > > Instead of uusing CMake modules, I have great experiences with using the > > cmake-config system. Which means that it is each component that have the > > cmake > > machinery. It also makes finding a library somewhat faster, and it is easier > > to have multiple versions installed. > > > > I have seen a few of these in the KDE-source, so i believe it is in line > > with > > the KDE mindset. > > Yep, all the libraries we write should provide a > LibraryNameConfig.cmake instead of a FindLibraryName.cmake. > > Of course the issue is finding all the libraries we don't provide...
Its not so much about what we provide vs. what we don't provide ourselves, but more about wether the project for that library uses cmake to build its code or not. In theory its perfectly possible to generate those XXConfig.cmake files without using cmake as buildsystem, but its a lot easier when cmake does this for you.. Andreas -- You will wish you hadn't. _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
