Issues for Qt5/KF5/KDE/CI system on OSX/MacPorts

[mk-lists at email.de]

Hi Ben,

On 26 May 2014, at 09:03 , Ben Cooksley <bcooksley at kde.org> 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
> solution allowing for them to be contained within the installation
> prefix is needed (whether assisted by OS X specific environment
> variables or through other mechanisms).
> 
> I wonder how Macports, Homebrew, etc. handle this.
Well, MacPorts tries very hard to keep all files in a dedicated
tree. The default install prefix is /opt/local. But when installing app
packages they usually get also linked into MacPorts’ installation
folder at /Applications/MacPorts/. KDE4 applications then land in the
subfolder  /Applications/MacPorts/KDE4/ which is why I would suggest
for KF5 simply to use /Applications/MacPorts/KF5.

But well, this is not to be done on the KDE/CI system. There I would 
suggest to place it below /Applications/KF5 for a start.


>> so, why don’t we send KDE’s apps to stg like
>>        /opt/kde/install/darwin/mavericks/clang/kf5-qt5/kf5/inst/bin
>> for a start?
> That is what should be happening. The KF5 CMake logic is disrespecting
> the install prefix we are specifying. This usually doesn't happen with
> executables - Qt plugins are notorious for having this issue though
> (as projects try to install them into the Qt installation prefix).
Yes, I had spotted that myself in the meantime and already sent a post.
Normal executables are obviously placed correctly, only application 
packages don’t get moved to where they should reside.

Greets,
Marko