Re: Anything left to do in CMake ?

2012-03-10 Thread David Faure
On Saturday 10 March 2012 16:25:57 Alexander Neundorf wrote: > Hi, > > I think things are looking quite good, and we got most of the things we > wanted to get into cmake in. > > Is something still left which should go into cmake ? Is there any chance to get the build type "DebugFull" into cmake?

Re: [kdelibs/frameworks-kcolors] /: Move khbox and kvbox from kdeui/widgets to staging/kwidgets/src/widgets

2012-03-10 Thread David Faure
On Wednesday 07 March 2012 15:17:13 Giorgos Tsiapaliwkas wrote: > Git commit d470e76948624257610bd7c583c442a542411093 by Giorgos Tsiapaliwkas. > Committed on 07/03/2012 at 15:16. > Pushed by tsiapaliwkas into branch 'frameworks-kcolors'. > > Move khbox and kvbox from kdeui/widgets to staging/kwidg

Re: KF5 Volunteer day 1: Done

2012-03-10 Thread David Faure
On Monday 27 February 2012 22:02:53 Kevin Ottens wrote: >- Manual tests in: staging/kguiaddons/tests You mean staging/kguiaddons/examples, I think. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5 _

Anything left to do in CMake ?

2012-03-10 Thread Alexander Neundorf
Hi, I think things are looking quite good, and we got most of the things we wanted to get into cmake in. Is something still left which should go into cmake ? * I'll try to get improved support for COMPONENTS in find_package() still into 2.8.8. * maybe FindLibLZMA.cmake * Anything else ? I w

KIcon API replacement (Re: patches on kcolors)

2012-03-10 Thread David Faure
On Saturday 10 March 2012 11:49:21 David Faure wrote: > Maybe we want to make it a method of > KIconLoader/KIconEngine instead? KIconLoader::loadIcon is already taken (and returns a QPixmap), and KIconEngine is an internal class. So a new suggestion would be: namespace KDE { QIcon loadIcon(c

Re: Which package will provide the common KDE library version number ?

2012-03-10 Thread David Faure
On Saturday 10 March 2012 12:18:06 Alexander Neundorf wrote: > To summarize: do you say it is ok to let every KDE frameworks git > repository decide for its own which versions of Qt and CMake it requires ? No, not if there is no good reason for it. I'm being pragmatic. konversation wants to keep

Re: Which package will provide the common KDE library version number ?

2012-03-10 Thread Ben Cooksley
On Sun, Mar 11, 2012 at 12:18 AM, Alexander Neundorf wrote: > On Saturday 10 March 2012, David Faure wrote: >> On Monday 27 February 2012 17:48:44 Alexander Neundorf wrote: >> > A common setup will be that "core" developers are building all frameworks >> > libraries. >> > Let's say some tier1 libr

Re: Which package will provide the common KDE library version number ?

2012-03-10 Thread Alexander Neundorf
On Saturday 10 March 2012, David Faure wrote: > On Monday 27 February 2012 17:48:44 Alexander Neundorf wrote: > > A common setup will be that "core" developers are building all frameworks > > libraries. > > Let's say some tier1 library, e.g. kcore needs Qt 5.1.2 and cmake 2.8.9. > > Another tier1 l

Re: patches on kcolors

2012-03-10 Thread David Faure
On Thursday 08 March 2012 18:23:56 Kevin Ottens wrote: > On Thursday 08 March 2012 18:08:15 Stephen Kelly wrote: > > David Faure wrote: > > > On Thursday 08 March 2012 13:11:37 Giorgos Tsiapaliwkas wrote: > > >> This is my patch about moving kdialog to staging/kwidgets but I need to > > >> link to

Re: Which package will provide the common KDE library version number ?

2012-03-10 Thread David Faure
On Monday 27 February 2012 17:48:44 Alexander Neundorf wrote: > A common setup will be that "core" developers are building all frameworks > libraries. > Let's say some tier1 library, e.g. kcore needs Qt 5.1.2 and cmake 2.8.9. > Another tier1 library, let's say solid, maybe says it needs Qt 5.1.0 a