[KDE/Mac] QStandardPaths possible solution
jpwhiting at kde.org
Thu Jan 8 23:48:46 UTC 2015
Just asked Thiago on irc and got the answer I should have known.
QLibraryInfo. So the question is should we use
QString::fromLatin1("/share") or is
QLibraryInfo::location(QLibraryInfo::DataPath) enough. A quick test in my
qt5.4 here shows those are both the same, but maybe that's because I did
-developer-build when I configured, so I wouldn't need to make install.
On Thu, Jan 8, 2015 at 4:29 PM, René J.V. <rjvbertin at gmail.com> wrote:
> On Thursday January 08 2015 23:57:55 David Faure wrote:
> > So yeah, I guess QT_INSTALL_PREFIX/share is your best bet.
> > But we'll see if other QtCore people have a better idea.
> That would work, but we'd still need to get it either into a config.h
> equivalent (qconfig.h?), or at the right place in a compiler argument list
> (with -D).
> I've tried to ask for some guidance on this on the interest ML, but got
> redirected to the development ML.
> I'd just as well not subscribe to YAML; is/are any of you subscribed?
> > Hello,
> > We're working on a patch for QStandardPaths on Mac OS X that will add an
> > XDG-compliant element to the search path, an element that is known at
> > compile time. A review request will soon be made for this change
> > the situation in more detail. We figured that the best way to implement
> > this would be to add a preprocessor macro that is defined at configure
> > when an option such as -xdg-compliant-path= is given to configure. That
> > macro would contain the additional search path element, and which is also
> > used to activate the modified code so that no changes are made as long as
> > the configure option isn't given (the default). None of us have
> > knowledge of the configure and build system, so some guidance would be
> > welcome.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kde-mac