cmake

[Thomas Zander]

On Thursday 8 June 2006 18:40, Alexander Neundorf wrote:
> > The issue is that cmake tries to make all subtrees behave like one
> > tree while using a lot of makefiles and with the limitations of POSIX
> > make this is just a recipe for failure.  This is the design flaw I'm
> > looking at.
>
> I handles trees as one big project and since the apps and libs in the
> tree depend on each other I don't see the design flaw in this approach.

The fact that it handles trees as one big project and thus has a different 
definition of 'subproject' as make and unsermake had is the problem 
indeed.

That you don't see that as a problem only means that you misunderstood the 
requirements KDE developers[1] have of their buildsystem.


1) I hardly can speak for all developers, but all people I spoke to saw 
this issue as a problem.
-- 
Thomas Zander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060608/bd3e4792/attachment.sig>