----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105863/#review16879 -----------------------------------------------------------
tier2/kconfig/CMakeLists.txt <http://git.reviewboard.kde.org/r/105863/#comment13213> Ah, damn, there are conflicting goals here. We removed ${CMAKE_MODULE_PATH} on purpose so that each framework (in this case, tier2/kconfig) builds standalone, i.e. doesn't use any cmake file from the rest of kdelibs. As long as we have independent frameworks being built together in one big kdelibs (which is a temporary situation), this is a way to ensure that each module is self-contained in terms of cmake files. Now let's talk about FindKDEWin.cmake: can't we get rid of that? Try to think of kconfig as "a pure Qt-based library", like say, soprano, qca, or qjson. These libs don't use and don't need FindKDEWin.cmake, right? So why would kconfig need that additional layer? I know it was a necessary layer to get KDE4 code to compile on Windows, but the goal with KF5 is to remove layers and ensure that Qt and cmake have everything we need to compile our standalone libs on top of them. Please evaluate what needs the "kdewin" (library, right?), and whether that code can't be ported to "pure Qt" instead. - David Faure On Aug. 4, 2012, 9:11 p.m., Andrius da Costa Ribas wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/105863/ > ----------------------------------------------------------- > > (Updated Aug. 4, 2012, 9:11 p.m.) > > > Review request for KDE Frameworks and Patrick Spendrin. > > > Description > ------- > > Keep the paths already in CMAKE_MODULE_PATH when adding ECM_MODULE_PATH and > other search-paths into it. > > > Diffs > ----- > > CMakeLists.txt f20069c > tier2/kconfig/CMakeLists.txt c4b2cf6 > > Diff: http://git.reviewboard.kde.org/r/105863/diff/ > > > Testing > ------- > > Before this adjustment it was not possible to proceed with the build due to > missing Find*.cmake (e.g.: FindKDEWin.cmake) files. > > > Thanks, > > Andrius da Costa Ribas > >
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
