<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 2 February 2016 at 04:18, Andre McCurdy <span dir="ltr"><<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@gmail.com</a>></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"><div id=":3fr" class="" style="overflow:hidden">Thanks. Unfortunately I don't see a clean solution for this. The<br>
setup.py script uses curl-config to determine which ssl implementation<br>
curl has been built against and that information isn't available from<br>
pkg-config.<br>
<br>
It's probably fixable with some surgery, but I'm not sure it's worth<br>
the maintenance effort just so we can disable curl binconfig...<br>
<br>
Please drop my "curl: disable curl-config binconfig file" patch.</div></blockquote></div><br>The feature tests? That's exposed in pkg-config as the supported_features variable. I wouldn't be surprised if more recipes in meta-oe were using curl-config though, so I do agree with you here: moving away from curl-config would be good but scoping out the damage in a world build including meta-oe needs to be done first.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>