Re: using kde4support

2013-03-06 Thread Sebastian Kügler
On Wednesday, March 06, 2013 13:08:13 Marco Martin wrote: > Hi all, > there are at the moment some problems linking to the kde4support library > from plasma-framework (yes, we'll eventually port out of it, but one thing > at a time ;) > > in the cmake i do > find_package(kde4support REQUIRED) >

Re: State of the buildsystem in KF5

2013-03-06 Thread Sebastian Kügler
On Wednesday, March 06, 2013 19:32:44 Alexander Neundorf wrote: > here's a really short summary of the current state of the buildsystem in > kdelibs. > > kdeqtstaging, all libraries in tier1/ and all libraries in tier2/ can be > built as part of kdelibs, or each one separately stand-alone. > So,

Re: Please update extra-cmake-modules, kdelibs (and plasma-frameworks)

2013-03-06 Thread Stephen Kelly
Alexander Neundorf wrote: >> That may be a broader issue, but I don't think this is a problem for KDE. >> For the KDE frameworks, we will use the KF5:: prefix. > > If we start doing it here, our developers will assume this is the way to > do it and take this everywhere, at their workplaces, to oth

Re: making changes in kdelibs[frameworks]: don't kill us kittens

2013-03-06 Thread Ben Cooksley
On Thu, Mar 7, 2013 at 6:44 AM, Alexander Neundorf wrote: > On Wednesday 06 March 2013, Sebastian Kügler wrote: > ... >> Also, please pay close attention to jenkins kdelibs *AND* plasma-frameworks >> builds. It doesn't catch everything (IME, not sure why), but the more, the >> merrier: >> >> kdeli

State of the buildsystem in KF5

2013-03-06 Thread Alexander Neundorf
Hi, here's a really short summary of the current state of the buildsystem in kdelibs. kdeqtstaging, all libraries in tier1/ and all libraries in tier2/ can be built as part of kdelibs, or each one separately stand-alone. So, except still needing kdeqtstaging, the buildsystems in tier1/ and tier

Re: Please update extra-cmake-modules, kdelibs (and plasma-frameworks)

2013-03-06 Thread Alexander Neundorf
On Tuesday 05 March 2013, Stephen Kelly wrote: > Alexander Neundorf wrote: ... > > * Using imported target names directly extends the scope of cmake source > > compatibility. > > I don't think I understand. In your opinion, should using target names > directly not carry an expectation of source co

Jenkins build became unstable: kdelibs_frameworks_qt5 #475

2013-03-06 Thread KDE CI System
See ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: making changes in kdelibs[frameworks]: don't kill us kittens

2013-03-06 Thread Alexander Neundorf
On Wednesday 06 March 2013, Sebastian Kügler wrote: ... > Also, please pay close attention to jenkins kdelibs *AND* plasma-frameworks > builds. It doesn't catch everything (IME, not sure why), but the more, the > merrier: > > kdelibs: http://build.kde.org/job/kdelibs_frameworks_qt5/ > plasma: http

making changes in kdelibs[frameworks]: don't kill us kittens

2013-03-06 Thread Sebastian Kügler
Hi, In the plasma team, while working on the frameworks port, we run into "unexpected changes" quite often. In most cases, something in kdelibs[frameworks] or in e-c-m changed, and we only find out the hard way, and then have to sift through git logs, patches, cmake files etc. to sort it out a

using kde4support

2013-03-06 Thread Marco Martin
Hi all, there are at the moment some problems linking to the kde4support library from plasma-framework (yes, we'll eventually port out of it, but one thing at a time ;) in the cmake i do find_package(kde4support REQUIRED) and then add ${kde4support_LIBRARY} to target_link_libraries but the li

Re: kdelibs frameworks buildsystem under Windows

2013-03-06 Thread Laszlo Papp
On Tue, Mar 5, 2013 at 5:14 PM, Alexander Neundorf wrote: > It would be nice (I mean *really* nice) if somebody from the Windows team > could have a look at the cmake code and give integrating thwe manifest > support > stuff for mingw a try. > Otherwise I think we'll have a serious problem with K