https://bugs.kde.org/show_bug.cgi?id=393946
Bug ID: 393946
Summary: Problem looking up libexec binaries in .DMG bundled
apps on Mac
Product: Craft
Version: master
Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Core
Assignee: vonr...@kde.org
Reporter: thomas.friedrichsme...@ruhr-uni-bochum.de
CC: kde-windows@kde.org
Target Milestone: ---
A tester has run into the following bug when opening the "file browser" tool
window of RKWard, installed from a Mac .DMG, created on the binary factory.
While, here, it is about kioslave, I suppose that similar bugs will be lurking
at various other place related to "libexec" binaries:
Unable to create io-slave. Can not find 'kioslave' executable at
'/Users/rkward/Music/rkward.app/Contents/MacOS, /Users/rkward/Music/
rkward.app/Contents/libexec, /Users/packaging/Craft/BinaryFactory/
macos-64-clang/lib/libexec/kf5'
Now, this corresponds to the follow source code in kio:
https://cgit.kde.org/kio.git/tree/src/core/slave.cpp#n506
I.e. these paths correspond to QCoreApplication::applicationDirPath(),
QLibraryInfo::location(QLibraryInfo::LibraryExecutablesPath), and then the
compile-time path, respectively.
For Mac, neither the first nor third would be suitable options (but notably,
the third path is probably hiding the bug from developers!).
QLibraryInfo::LibraryExecutablesPath should be usable, but not trivially so:
1. The "libexec"-folder is at XYZ.app/Contents/Frameworks/libexec, and that
does seem more reasonable than XYZ.app/Contents/libexec . If we want to use
that, one way will be to append to qt.conf (already created by macdeployqt):
"LibraryExecutables = Frameworks/libexec"
2. However, the follow-up problem is that most binaries are in subfolders
"kf5"/ "kauth". This is not where the above code is looking, however. It looks
directly in libexec . So the installation directory should probably omit the
"kf5" as on Windows
(https://cgit.kde.org/extra-cmake-modules.git/tree/kde-modules/KDEInstallDirs.cmake#n441).
--
You are receiving this mail because:
You are on the CC list for the bug.
