<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 24 May 2017 at 14:52, Mike Crowe <span dir="ltr"><<a href="mailto:mac@mcrowe.com" target="_blank">mac@mcrowe.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=":1a6" class="a3s aXjCH m15c3abb64b3fca77">Oh, I thought that binconfig.bbclass swung through hoops in order to make<br>
the scripts work well enough. Is that not true?<br>
<br>
Many other recipes are still inheriting binconfig rather than<br>
binconfig-disabled: apr, curl, gnutls, libtasn1.</div></blockquote></div><br>binconfig goes through hoops that are just not required with pkgconfig, and the hoops are hacks which may not be reliable. I can't remember the details but I do remember that libgcrypt/gnupg was a worst offender here.</div><div class="gmail_extra"><br></div><div class="gmail_extra">CCing Richard to see if he can remember why.</div><div class="gmail_extra"><br></div><div class="gmail_extra">In the glorious future removing all binconfig scripts would be the ideal, in my opinion. Alternatively replacing them with glorified pkgconfig wrappers.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>