https://bugs.kde.org/show_bug.cgi?id=410240
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caulier.gil...@gmail.com,
| |rjvber...@gmail.com
--- Comment #7 from caulier.gil...@gmail.com ---
To Maik, comment #3 :
QStandardPath is problematic under MAcOS, especially for KF5 based API and
application.
The vision to handle QStandardPath from KF5 team and Qt5 team is completely
different. As i know this divergence is not yet resolved in source code.
So to join dots, i write a shell script, which patch automatically
QStandardPath call everywhere before to compile codes when we build MacOS PKG :
https://cgit.kde.org/digikam.git/tree/project/bundles/macports/fixbundledatapath.sh
Called here :
https://cgit.kde.org/digikam.git/tree/project/bundles/macports/03-build-digikam.sh#n105
https://cgit.kde.org/digikam.git/tree/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt#n128
https://cgit.kde.org/digikam.git/tree/project/bundles/3rdparty/ext_marble/CMakeLists.txt#n59
But i doubt that the problem come from this patch, else nothing will work
properly, as the KXMLGui XML definition will not be loaded and GUI will appear
without menu for example.
I thinking more about a wrong path used to package icons in the bundle.
About the Qt5/KF5 conflict about QStandardPath, i CC Renee J Bertin, who know
better than me the story and if the issue will be finally closed in the future.
Gilles Caulier
I CC
--
You are receiving this mail because:
You are watching all bug changes.
