That does sound like a bit more interesting question. Browsing through http://lxr.kde.org/ident?_i=QStandardPaths&_remember=1 (quite a long list...) a couple of things come to mind. First anything that's using QStandardPaths isn't necessarily using any frameworks at all. Looking at http://agateau.com/2013/kf5-diagrams/kf5.png (which admittedly may not be up to date either) it seems KCoreAddons is a very commonly used framework. Also depended on by many other frameworks and used by many applications. It contains KAboutData which is used by pretty much any GUI application that we release, I'm not sure if it matters if it needs to be used by command-line tools also or not. I'm not sure how many if any command line tools or system daemons etc. are using QStandardPaths. Maybe try with KCoreAddons and see if that's a suitable enough place?
BR, Jeremy On Thu, Sep 24, 2015 at 3:34 AM, René J.V. <rjvber...@gmail.com> wrote: > In fact, let me ask a different question: is there a KF5 framework that is > guaranteed to be linked to by all KF5 applications that have reason (or are > likely) to query QStandardPaths for locations? > That would probably provide the cleanest and easiest solution to my quest: > that framework could be patched (on OS X or for MacPorts/Fink/...) to > activate the QSP mode switch. (And that could be either using an instance of > the dedicated class I described, or using an OS X framework initialisation > routine.) > > R. _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
