On 15.08.11 21:28:41, Valentin Rusu wrote: > Hello Alex, > > I'm giving the SuperBuild a try. I'd also like to build the whole KDE in > a fresh new prefix, namely /home/kde. > > I cloned Qt in /home/kde/src/qt and built it with the right prefix. > I clone SuperBuild in /home/kde/src/superbuild and looking into it I see > that the first thing these scripts do is: > > find_package(Qt4 REQUIRED) > > Seems that FindQt4.cmake must be located somewhere. > > > locate FindQt4.cmake > This command found several copies of this file (though I didn't open > each one to check if it's they share the same contents). > > Suppose now I'm starting building KDE in a new box, without > FindQt4.cmake. I won't be able to do it.
Yes you will, FindQt4.cmake is part of cmake itself and hence its always there. > I propose that SuperBuild holds a set of a minimum of cmake modules > needed to bootstrap the building environment. Something like a directory > superbuild/cmake/modules holding FindQt4.cmake, for instance. I did not look at what superbuild does exactly, but all projects 'below' kdelibs in the dependency chain need to have their own cmake modules in them and set the cmake module path accordingly or rely on modules that cmake ships itself. kdelibs ships a couple of modules and installs some of them and also makes sure those are found during cmake time. Andreas _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
