On Saturday 09 May 2009, Sune Vuorela wrote: > On Wednesday 06 May 2009 23:12:35 Alexander Neundorf wrote: > > On Wednesday 06 May 2009, Aaron J. Seigo wrote: > > > SVN commit 964099 by aseigo: > > > > > > builds with kdelibs, but -should- also be buildable separately. there's > > > still the issue of the FindLibKNotificationItem.cmake file outstanding, > > > or does that not matter now that it's in kdelibs/experimental/? build > > > system guidance desired. CCMAIL:[email protected] > > > > > > > > > M +1 -0 CMakeLists.txt > > > M +1 -1 > > > experimental/knotificationitem/knotificationitemprivate_p.h M +5 -4 > > > experimental/knotificationitem/test/knotificationitemtest.cpp > > > > Ok, so now we have a modular build of kdelibs. > > > > What should be supported ? > > > > 1) Building and installing complete kdelibs in one go, and having > > everything available by just doing > > find_package(KDE4) ? > > I don't think find_package(KDE4) should find anything but "real kdelibs", > and as the experimental parts are packaged seperately, it neeeds two > checks.
Technically it's the same as when e.g. building plasma or khtml separately, so I'd like to handle it the same way. I.e. after find_package(KDE4) no additional find_package(khtml) should be necessary, but instead either if(KDE4_KHTML_FOUND) or if (KDE4_KHTML_LIBS) should be checked. Since also experimental can be built as part of kdelibs, I would prefer doing it the same way. > I'm not that interested in making it possible to install the experimental > parts in a different destination. :-) Alex _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
