my little tooth on cmake

Jaison Lee lee.jaison at
Fri Mar 17 16:27:13 GMT 2006

On 3/17/06, Adriaan de Groot <groot at> 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.

I think this is a conversation best for kde-buildsystem, because I
know the cmake devs pay attention to that list. Have either of you
brought this up with them? It seems clear to me that the recent
changes to cmake will eventually be rolled into a cmake release. We're
just ahead of the ball right now. And qt-copy is hardly new, and is
kept for basically the same reasons.

And honestly, at this point in development if you're not content to
recompile frequently then you should probably wait things out for a
little while longer. :P

More information about the kde-core-devel mailing list