> On Mon, Mar 14, 2011 at 6:01 PM, Ilya Chernykh <neptunia@...> wrote:
>> On Monday 14 March 2011 23:19:40 Timothy Pearson wrote:
>>
>>> Not to mention the time required for building the following packages:
>>>
>>> kdelibs:
>>> with Automake: 50 minutes
>>
>> Even with parallel compiling?
>
> Parallel compiling would probably speed things up, but looking at the
> results, cmake would still likely be faster when comparing both in
> parallel.
>
> I remember seeing somewher (I think either IRC or the wiki, will have
> to check) that some of the stuff doesn't build will in parallel, while
> some of it does
>

This is true.  kdelibs/kdebase don't build in parallel due to some sort of
Automake glitch.


As I mentioned before, it is just too easy to mess Automake up in a
variety of very hard to trace ways.  I can attest to this; the latest
autoconf versions won't even find certain core libraries any more. 
Nothing changed in the Trinity automake files, and I have been unable to
resolve the problem despite spending several weeks looking for a fix.

CMake is the future--it offers more functionality, faster build times,
less opportunities for breakage, and to top it all off no functionality is
lost compared to Automake.

Tim