On Saturday, May 24, 2014 02:09:13 AM mk-li...@email.de wrote:
> Hi,
>
> I am trying to set up a KDE Continuous Integration system on OSX/MacPorts [1]
> and thanks to Ben Cooksley I managed to get it going quite far, since Qt5 and
> all tier 1 frameworks are installing just fine! :-)
>
>
Very
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118270/#review58411
---
Thanks for the fix, it seems to work fine.
I built KDE SC 4.13
In data sabato 24 maggio 2014 14:30:03, mk-li...@email.de ha scritto:
> On 24 May 2014, at 12:43 , Luigi Toscano wrote:
> > See for example: https://git.reviewboard.kde.org/r/115752/
>
> Yep, I think Harald’s patch should do the job, also on MacPorts!
> Will test it myself.
Maybe, but there is a
On 24 May 2014, at 12:43 , Luigi Toscano wrote:
> See for example: https://git.reviewboard.kde.org/r/115752/
Yep, I think Harald’s patch should do the job, also on MacPorts!
Will test it myself.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel
On 24 May 2014, at 13:31 , Martin Graesslin wrote:
> The plan is to move the daemon back into the framework, but that requires
> some
> more work to not have it end as a tier3.
The irritation arises on my end only because the framework does actually build
on OSX…
Does it mean it just wouldn’t
On Saturday 24 May 2014 02:09:13 mk-li...@email.de wrote:
> 2.2) kcompletion using
> /Applications/KDE/kconfig_compiler_kf5.app/Contents/MacOS/kconfig_compiler_
> kf5 as location is wrong [3]
The issue here is with the KConfig framework, and specifically something in
src/kconfig_compiler/CMakeLi
On Saturday 24 May 2014 12:28:52 mk-li...@email.de wrote:
> 2)
> KGlobalAccel is also marked invalid for OSX:
>
> This framework also builds and deploys, but we had quite a discussion
> lately about kglobalaccel integration on MacPorts/KDE 4.12.* in order to
> get KDE build fine on MacPorts
In data sabato 24 maggio 2014 02:09:13, mk-li...@email.de ha scritto:
> 3.3) kjsembed (kdoctools can't find its catalogs) [5]
>
>
> I could imagine that 2.2, 3.2 and 3.3 can be fixed easily.
> [...]
> [5] http://paste.kde.org/rev/pmjob21rt
I suspect this is the (still undecided) issue with the
Some additional questions:
1)
KDE’s apidoc states that kcrash and kpty are invalid for MacOSX [1]:
But I am able to build and deploy those frameworks no problem.
(Not sure about tests now, though.)
2)
KGlobalAccel is also marked invalid for OSX:
This framework also bui
Hi,
I am trying to set up a KDE Continuous Integration system on OSX/MacPorts [1]
and thanks to Ben Cooksley I managed to get it going quite far, since Qt5 and
all tier 1 frameworks are installing just fine! :-)
But I have trouble with the next tiers:
Tier 2:
2.1) kauth depends on currentl
10 matches
Mail list logo
