libexec (Re: "kde5" or "kf5" ?)

[David Faure]

On Saturday 23 February 2013 19:05:34 Alexander Neundorf wrote:
> At configure/cmake time, we can configure e.g. the data install dir, the
> lib  install dir and the install prefix into the library.
> At that point, we can check whether both are installed into the same
> prefix,  independent of whether absolute or relative paths are used for
> installing.
> 
> So we can configure the relative path to the data and to the library into
> the  library, so we have then e.g. "share/kio/" and "lib/<multiarchdir>/"
> in the library.
> At library runtime we can find out the location of the library, check that
> it  contains the configured relative library install path, and if so,
> remove that part, and we have the install prefix at library runtime.
> (I can create an example for that)

OK, I understand the idea now. Note that this still only works "for files 
installed by kio and looked up by kio", not for *any* lookup of these files 
happening elsewhere (e.g. from within Qt code). But OK, one problem at a time.

The other problem I see, is where to put all that code. The only way to share 
this "magic determination of install dirs" code without introducing more 
dependencies would be to have it in Qt... Well, we could start in kcoreaddons 
I guess, since tier1 libs will hopefully not need this themselves.
Looking at "make install" output, they don't indeed.
(And in the current tier2, the only runtime files seem to be from kauth: 
share/kauth/*.stub, and two plugins.)

I think we have many more urgent things to work on, though, but I won't stop 
you.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by BlueSystems and KDAB to work on KDE Frameworks