[Development] QStandardPaths could be helpful for cross platform portability, Qt Everywhere

Jeremy Whiting jpwhiting at kde.org
Wed Feb 25 13:26:06 CET 2015

Tor Arne,

As a test I modified my setup on OS X yesterday to pass
-DCMAKE_INSTALL_DATADIR="/Users/jeremy/Library/Application Support/" to
every KDE module's cmake comand. This successfully installed all supporting
data files into ~/Library/Application Support/foo and only required a
couple of minor changes to KF5FooConfig.cmake files so these data files
(mostly scripts, but also the previously mentioned xsl data files) could be
found when building other libraries or applications that depend on foo. So
far everything "just works" as it did with the QSP patch. I.e. stuff that's
broken on OS X is still broken, but those are other issues. I'll write up a
suggestion on the KDE mailing lists today about how best to make these
changes OS X specific whether that be having separate FooConfig.cmake.in
files for OS X or by changing them to be more cross platform anyway, we'll


On Wed, Feb 25, 2015 at 4:51 AM, Tor Arne Vestbø <tor.arne.vestbo at digia.com>

> On 25/02/15 12:31, Tor Arne Vestbø wrote:
>> This should be fixed for OS X (and iOS). ~/Library/Application Support
>> can be used for installed application data, but is most typically used
>> for generated application data that is not directly user documents
>> (which should live in ~/Documents), so the app bundle should be one of
>> the paths returned by QStandardPaths.
> And looking at the QSP docs, this should already be the case:
> "~/Library/Application Support/<APPNAME>", "/Library/Application
> Support/<APPNAME>". "<APPDIR>/../Resources"
> tor arne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150225/7c730ee6/attachment.html>

More information about the Development mailing list