<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Mar 24, 2014 at 5:29 PM, Alex Merry <span dir="ltr"><<a href="mailto:alex.merry@kde.org" target="_blank">alex.merry@kde.org</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Currently, paths to libexec files are hardcoded (or not... see<br>


<a href="https://git.reviewboard.kde.org/r/117023/" target="_blank">https://git.reviewboard.kde.org/r/117023/</a>).  This works find unless you<br>
want to relocate anything.<br>
<br>
I know that relocating is something that has come up with KDE on Windows<br>
stuff.  Is it something we want to support?  If so, how would we do it?<br>
<br>
I think most of the rest of our stuff (including CMake code) supports<br>
relocation, even if you have to set some environment variables to<br>
support it (like LD_LIBRARY_PATH on Linux).<br>
<br>
Alex<br>
_______________________________________________<br>
Kde-frameworks-devel mailing list<br>
<a href="mailto:Kde-frameworks-devel@kde.org">Kde-frameworks-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-frameworks-devel" target="_blank">https://mail.kde.org/mailman/listinfo/kde-frameworks-devel</a><br>
</blockquote></div><br></div><div class="gmail_extra">I just saw that Qt itself is already installing things in <prefix>/libexec (e.g. libexec/QtWebProcess). We probably want to do the same.</div><div class="gmail_extra">

<br></div><div class="gmail_extra">Also it would be interesting to see how they are finding the executables and maybe mimic it ourselves.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Personally, I think that it doesn't make sense that we're hardcoding paths while everything is abstracted and magic.</div>

<div class="gmail_extra"><br></div><div class="gmail_extra">Aleix</div></div>