my little tooth on cmake

Allen Winter winter at
Fri Mar 17 17:11:15 GMT 2006

On Friday 17 March 2006 10:15, Adriaan de Groot wrote:
> On Friday 17 March 2006 15:54, Cristian Tibirna wrote:
> > development. I.e., you have to actually _compile_ cmake (successfully! and
> > the right version! which is now a rather fast moving target) before even
> > coming close to compile KDE.
> Amen. This was the crux of my recent question here related to cmake and 
> kdebase. Alex suggests CVS HEAD of cmake for now. It certainly doesn't make 
> progress any easier when you can wake up in the morning and need to compile a 
> new cmake and new qt-copy before checking to see if kdelibs is still working.
> I don't think a copy of cmake is an answer, though, since that just means that 
> you need to update and rebuild cmake from the copy every day.

For now, how about putting a copy of cmake into trunk/kdenonbeta alongside unsermake.
Then make building/installing cmake a requirement.  Ideally the build instructions change
from "add unsermake to your $PATH" to "add cmake to your $PATH".

Eventually the distros will have to start providing cmake binaries.


Let's Keep the Political Talk Out of KDE PLEASE

More information about the kde-core-devel mailing list