On 3 November 2011 22:04, Darrell Anderson <humanreadable@...> wrote:
In a past thread conversation I was told I MUST use cmake to build tqtinterface, arts, kdelibs, and kdebase. So far so good.

I was told to use autotools for the remaining packages. Yet the 3.5.13 wiki says kdeartwork, kdesdk, kdegraphics, kdepim, kdenetwork, kwebdev, and kdevelop have been ported to cmake. Are those complete ports? That is, do I use cmake for those packages or autotools?



To unsubscribe, e-mail: trinity-devel-unsubscribe@...
For additional commands, e-mail: trinity-devel-help@...
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

I use cmake for everything I can, it all works splendidly.

The more we use cmake the better. It's faster, easier to work with, and less confusing than automake