On Saturday, 17 de September de 2011 10:54:25 David Faure wrote: > Does Qt have the concept of a libexec directory? > I.e. a directory that contains executables that are used by library code, > and that shouldn't be in $PATH so as not to bother users. > > I'm porting code to QStandardPaths::findExecutable, and realizing that it > only looks in PATH, so it doesn't have support for other directories like > libexec. But I don't see how it could "guess" where to look, since this > isn't typically determined by an environment variable... > > (For an example of what this is all about, ls /usr/lib*/kde4/libexec/)
The KDE 4 libexec is also new in KDE 4. In KDE 3 we used to pollute /usr/bin
with out helper tools. I still want to run kdontchangethehostname every now
and then to see what it does :-)
I think the concept is a valid one and should be reflected in QStandardPaths. I
just don't know where to get the list of paths.
As it stands right now, Qt has no helper executables, so we've never needed to
find them from Qt code. Applications and other libraries have done that for
themselves.
Tell me this: how would you write code that searches for a generic libexec (no
"kde4" in the pathname) and yet allows KDE to find its helper tools?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
