The Technical Working Group's mission statement

R.F. Pels ruurd at tiscali.nl
Tue Mar 14 20:22:08 GMT 2006


On Tuesday 14 March 2006 20.10, Kurt Pfeifle wrote:

>>> If it's a matter of decisions, then let's decide: cmake or autotools?
>>
>> No kdevelop support for cmake, then, no cmake
>
> Are you saying that cmake can only be used for KDE4 development
> *after* kdevelop starts to support cmake?
>
> You are not content with what we have "the other way round", namely
> the *already* available cmake support for kdevelop?
>
> You are not confident that someone will extend kdevelop during
> the next few months to add cmake support to it, and want to stay
> with automake until that happens?

Maybe a bit too bold. Let me rephrase. I think it is very important that cmake 
is properly supported in kdevelop if cmake is the buildsystem for KDE. If 
there is proper and reasonably robust twoway support between the cmake 
infrastructure and the kdevelop project manager, I am inclined to say go 
ahead and switch to cmake. If that is not the case or if there is no 
expectation that that is going to be the case in the near future, I would be 
inclined to think long and hard before actually deciding on cmake as the KDE 
build system.

As for the confidence part: let's say my confidence will be bigger if the TWG 
would decide to coordinate an effort to get to a above situation (proper and 
reasonably robust cmake support) between the kdevelop maintainers and the 
cmake build infrastructure maintainers. 

-- 
R.F. Pels,  3e Rompert 118,  5233 AL  's-Hertogenbosch,  The Netherlands
+31736414590        ruurd at tiscali.nl       http://home.tiscali.nl/~ruurd





More information about the kde-core-devel mailing list