> On Mon, Mar 14, 2011 at 5:04 PM, Darrell Anderson
> <humanreadable@...> wrote:
>> As I wrote in my previous post, I haven't YET given up.
>>
>> Yes, I have noticed the build time difference with tqtinterface, arts,
>> kdelibs, and kdebase. :) Thank you Serghei!
>>
>> The core Trinity modules are almost ported to cmake? Hmm. I don't see
>> that in my local svn tree. I updated svn yesterday. I see the following:
>>
>> tqtinterface
>> arts
>> kdelibs
>> kdebase
>> kdegraphics
>> kdevelop
>> kdewebdev
>> kdepim
>>
>> Core packages with no CMakeLists.txt:
>>
>> kdebindings
>> kdeaccessibility
>> kdeutils
>> kdemultimedia
>> kdenetwork
>> kdeadmin
>> kdeartwork
>> kdegames
>> kdetoys
>> kdeedu
>> kdeaddons
>> kdesdk
>>
Also, the ones that you list directly above (accessibility, utils, etc.)
are relatively simple build-wise.  libs, base, pim, kdevelop, etc. are NOT
simple and they have taken longer to port to CMake.

If someone wanted to try to get Automake repaired for the modules for
which CMake is not yet ready, that's fine with me, as long as it does not
detract from the CMake effort.  I will not be able to help in that effort,
as I am working on building Debian packages and fixing bugs.  Personally,
having looked at CMake's build files, I believe it to be a far better
solution.  There were too many ways Automake could fail, as I think
Darrell knows. ;-)

Tim