<div dir="ltr">On 12 December 2017 at 07:48, Stefan Agner <span dir="ltr"><<a href="mailto:stefan@agner.ch" target="_blank">stefan@agner.ch</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2017-12-11 18:15, Otavio Salvador wrote:<br>
> On Mon, Dec 11, 2017 at 3:09 PM, Burton, Ross <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br>
>> On 11 December 2017 at 15:37, Joshua Watt <<a href="mailto:jpewhacker@gmail.com">jpewhacker@gmail.com</a>> wrote:<br>
>>><br>
>>> Vanilla waf only supports --prefix, --libdir, and --bindir. Anything else<br>
>>> is a result of loading the gnu_dirs tool, which not all projects are<br>
>>> required to do.<br>
>>><br>
>>><br>
>>> Sorry, hit send too soo: waf (at least version 2.0) also errors out on<br>
>>> unknown options. I think the three I listed are the only ones we can do<br>
>>> generically. There might be some way to easily adding the rest if you know<br>
>>> waf is loading gnu_dirs<br>
>><br>
>><br>
>> One option would be for waf.bbclass to check if WAF_USES_GNU_DIRS is set<br>
>> (defaulting to 0) and pass the full set of path options automatically.<br>
><br>
> Possible. But passing the standard ones solve 99% of the issues.<br>
><br>
<br>
</span>I am with Otavio here. Also, adding the standard ones and adding the<br>
additional GNU_DIRS would best be done in two independent patches<br>
anyway. For now I'd rather prefer to only add the standard ones.<br></blockquote><div><br></div><div>Fine by me. Will there be a v2 adding --bindir?</div><div><br></div><div>Ross </div></div></div></div>