On 14.04.11 21:59:24, Ian Wadham wrote: > On Thursday 14 April 2011 4:34:08 pm Andreas Pakulat wrote: > > On 14.04.11 16:00:11, Ian Wadham wrote: > > > Now kdesrc-build-1.13 reports the first failure on strigi. After that, > > > no major modules will build build. Re strigi, I get the messages: > > > > Looks like either someone broke the strigi repository, or your cmake > > cannot handle Git submodules that well. I recall a related bugfix in > > cmake 2.8.3 or 2.8.4. > > > Thanks, Andreas. > > What version of Cmake is required now in KDE? I have 2.8.2, built on > 30 June last year and I am not aware of any later version being required > (nothing found in Techbase post-2.8.2), but I have been out of touch > with KDE for most of the last 9 months. Cmake 2.8.2 built KDE OK for me > early in January and Cmake's latest version on www.cmake.org is 2.8.4, > released 16 Feb 2011.
2.8.2 is fine for building KDE, but this is not KDE code, you'll have to talk to the strigi-authors about their requirement. > > If updating cmake does not help, you can try to > > update the submodules manually, go to the strigi repository then do > > > > git submodule init > > git submodule update > > > I don't think a git novice (ignoramus) like me should be dinking with > KDE's git repository, if that's what you mean. No, you run this in your local clone of the strigi repository. Not sure wether you're aware of this, but the single strigi module was split into multiple git repositories. Apparently there's now also a 'meta repository' called "strigi" which uses the git submodule feature to merge back all the different strigi-related git repositories into 1 local checkout. Doing this requires to use the git submodule command after having cloned the meta-repository and it looks like your cmake version is not able to do that for some reason. Andreas >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
