<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 26 February 2016 at 01:45, Hongxu Jia <span dir="ltr"><<a href="mailto:hongxu.jia@windriver.com" target="_blank">hongxu.jia@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":5al" class="a3s" style="overflow:hidden">+do_unpack[postfuncs] += "unpack_waf"<br>
+do_unpack[vardeps] += "unpack_waf"<br>
+unpack_waf() {<br>
+ # Just self extract tarball embedded in waf, do not care help message.<br>
+ # Do not generate bytecode, becuase we need to patch python file later<br>
+ PYTHONDONTWRITEBYTECODE=True ./waf --help >/dev/null<br>
+}<br></div></blockquote><div><br></div><div>Presumably this isn't pycairo-specific but impacts every recipe using waf?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":5al" class="a3s" style="overflow:hidden">
do_configure() {<br>
- BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} ./waf configure --prefix=${D}${prefix} --libdir=${D}${libdir}<br>
+ BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} ./waf configure --prefix=${prefix} --libdir=${libdir}<br>
}</div></blockquote></div><br>Looks like this recipe needs to use the waf class for a start.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>