<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 22 June 2017 at 09:42, Adam Trhon <span dir="ltr"><<a href="mailto:adam.trhon@tbs-biometrics.com" target="_blank">adam.trhon@tbs-biometrics.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=":3pe" class="a3s aXjCH m15cd172facb50c68">but I am not very happy about using PACKAGECONFIG_CONFARGS - it feels hacky, the<br>
arguments are not shown in cmake fail log and it cannot handle argumetns containing<br>
spaces. Is there a cleaner way to achieve this?<br></div></blockquote></div><br>Definitely don't use PACKAGECONFIG_CONFARGS: that has a well defined meaning and use, and that isn't it.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I don't see why as you control the repository why can't you just set the arguments in cmakelists, or the recipe itself? Either they're useful everywhere (cmakelists) or in OE builds (recipe).</div><div class="gmail_extra"><br></div><div class="gmail_extra">Anyway, you could do something like this:</div><div class="gmail_extra"><br></div><div class="gmail_extra">python() {</div><div class="gmail_extra"> d.appendVar("EXTRA_OECMAKE", " " + open(d.expand("${S}/oe_arguments.txt")).read()</div><div class="gmail_extra">}</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>