https://bugs.kde.org/show_bug.cgi?id=410240
--- Comment #10 from RJVB <rjvber...@gmail.com> --- (In reply to caulier.gilles from comment #7) > 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. Erm, no. KF5 code (mostly) uses QSP as it should, given how KF5 software is installed most of the time. The main problem lies in the conflict between platform requirements on "platform-native" install locations and schemas in QSP and in KDE's build system. In other words, KDE's build system is designed around the assumption of having shared resources in a central location, which happens to match with the standard Unix QSP implementation but not that for the Mac OS and MS Windows (which assume some form of sandboxing). Qt were never downright hostile against supporting a shared install schema/model on Mac and/or PC, I long had an exchange with David Faure about this, but ultimately we just never got around to coming up with something that would have stood a chance to be included in Qt. Either way that wouldn't have helped you here. > About the Qt5/KF5 conflict about QStandardPath, i CC Renee J Bertin, who Gilles, you should know how to write my name without changing my gender :P > know better than me the story and if the issue will be finally closed in the > future. You could look at Kate to see how embedding resources into the binary can be leveraged; the breeze icon theme even has a feature to help with this. That feature is documented but I think in the code only. -- You are receiving this mail because: You are watching all bug changes.
