Hi, I think the chances of a Qt application depending on glib on Mac OS X are extremely slim, given that glib is not part of the default system installation. I think the much more common case of a Qt application on Mac OS X is to just use Qt and the system APIs without any third-party library dependency. So I think it makes sense if our defaults align towards that use-case and with what apple recommends for applications. Their documentation makes a compelling case IMO:
https://developer.apple.com/library/mac/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html Simon ________________________________________ From: Development <[email protected]> on behalf of René J. V. Bertin <[email protected]> Sent: Tuesday, November 24, 2015 11:25 To: [email protected] Subject: [Development] glib's and Qt's RuntimeLocation [OS X] Hello, This is a follow-up question to one I posted yesterday. Looking into the paths used for QSP::RuntimeLocation in more detail I noticed that GLib has its own ideas, using $HOME/.cache on OS X: https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-get-user-runtime-dir I have the impression that it's not that uncommon to use glib from Qt-based applications; how (un)likely is it that the disagreement on the location of the user runtime directory will lead to issues? R PS: why did Qt choose ~/Library/Application Support for that location? Isn't the stuff stored there supposed to be volatile that doesn't need to survive reboots or end up in (Time Machine) backups? _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
