<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 8 October 2015 at 22:00, Christopher Larson <span dir="ltr">&lt;<a href="mailto:clarson@kergoth.com" target="_blank">clarson@kergoth.com</a>&gt;</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"><span class=""><div class="gmail_quote"><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"><span><div class="gmail_quote"><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"><div style="overflow:hidden">+       # Use relative path for S to avoid buildpaths in files<br>
+       relative_s=`python -c &quot;import os; print os.path.relpath(&#39;${S}&#39;, &#39;.&#39;)&quot;`<br>
+       cfgscript=&quot;$relative_s/configure&quot;</div></blockquote></div><br></span>Why not just use inline python here, rather than calling out to an external python process at task execution time?</blockquote></div><br></span>Oh, nevermind, of course oe_runconf can be run from any number of paths :)</blockquote></div><br>Why not use realpath?</div><div class="gmail_extra"><br></div><div class="gmail_extra">ross@flashheart ~/Yocto/poky/meta/recipes-devtools/qemu (mut)</div><div class="gmail_extra">$ realpath --relative-to=. ~/Yocto/poky/meta/recipes-support/mpfr/</div><div class="gmail_extra">../../recipes-support/mpfr</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>