why kdelibs?

Alexander Neundorf neundorf at kde.org
Sat Oct 30 17:48:51 BST 2010

On Friday 29 October 2010, John Layt wrote:
> The other issue is platform portability, stick with Qt and you know it
> works on every platform with no extra effort, even if the tools fall short
> in some areas.  Use kdelibs and you will have problems on Win and Mac
> trying to decide how to package and distribute.  Work is ongoing on Win to
> make it happen, but Mac appears to have stalled somewhat?
> Of course, once the splitting work is done, and it's easily portable, then
> eternal vigilance is needed to make sure it stays that way, which probably

We need people willing to spend time and effort on setting up and maintaining 
nightly builds for the different platforms and configurations.
On my.cdash.org the projects are set up, and in kdesdk there are ctest scripts 
to run these builds. The scripts work AFAIK on all systems (at least Linux, 
FreeBSD, Solaris, OSX, not sure about Windows).

Maintaining such a build (i.e. a machine which builds KDE *every day of the 
year* with always up-to-date dependencies) is a non-negligible amount fo work 
in itself.


More information about the kde-core-devel mailing list