Hi Alex & Ben,
On 26 May 2014, at 11:04 , Alex Merry wrote:
> -DCMAKE_INSTALL_BUNDLEDIR=some/relative/path
thanks to your hint I was able to insert a temporary workaround here on my CI
system
by supplying an additional configuration file for kconfig as this:
---
$ cat ~/scripts/config/build/kco
Hi Allen,
On 25 May 2014, at 00:43 , Allen Winter wrote:
> I have local patches to commit yet that fixes some of the issues you mention
> below.
great!
I am looking forward to hear from you.
Peeking into Harald Fernengel’s Homebrew recipe for kauth [1] I found out that
there seems to be no need
Hi Alex,
On 24 May 2014, at 14:57 , Alex Merry wrote:
> Where *is* kconfig_compiler_kf5 installed?
thanks again for pointing that out!
I’ve found it here:
---
$ find /opt/kde -name kconfig_compiler_kf5.app
$ find /Users/marko/WC/KDECI-builds/ -name kconfig_compiler_kf5.app
/Users/marko/WC/KDECI
I see now that Harald installed in the application package below
PREFIX/lib/kde5/libexec/ [1].
Here on the CI system I already do find an executable in an equivalent folder:
---
$ ls -l
/opt/kde/install/darwin/mavericks/clang/kf5-qt5/frameworks/kconfig/inst/lib/libexec/kf5
total 136
-rwxr-xr-x 1
Hi Ben,
On 26 May 2014, at 09:03 , Ben Cooksley wrote:
> This is because it was installed to /Applications/ within the
> installation jail (located at
> /Users/marko/WC/KDECI-builds/kconfig/local-inst in this instance).
Yep.
> I've no idea how OS X handles applications/executables - but a
> solu
Hi Luigi,
On 24 May 2014, at 17:10 , Luigi Toscano wrote:
> Maybe, but there is a reason if it was discarded; it's not the "final"
yes, because that patch doesn’t work anymore with the current file.
But it shouldn’t be hard to come up with a new patch.
Greets,
Marko
___
On 26 May 2014, at 09:35 , Ben Cooksley wrote:
> For reasons stated above, application packages cannot reside within
> /Applications.
> If they need to reside within a separate directory, we'll need to
> arrange this - however it needs to be within the installation prefix.
Well, sure, I don’t wan
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
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
11 matches
Mail list logo
