<div dir="ltr"><div><div>Mark, the main point of the question about "changing without side-effects" and not about "how to change one config option to another"<br><br></div>But Andre has already provided information, cheers for that.<br><br></div>Thanks for participation<br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-05-07 23:00 GMT+03:00 Andre McCurdy <span dir="ltr"><<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, May 7, 2018 at 7:17 AM, Mark Hatle <<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a>> wrote:<br>
> On 5/7/18 8:16 AM, Viacheslav Salnikov wrote:<br>
>> Alright, good point.<br>
>><br>
>> But what if I need to use openssl instead of gnutls on Target? Can it be changed<br>
>> without side effects?<br>
<br>
</span>The behaviour of curl when built with gnutls -vs- openssl in OE is not<br>
the same. There are things (maybe related to certificates?) which work<br>
fine with openssl but don't work with gnutls. Unfortunately I don't<br>
have many more details than that - all the OE distros I use have<br>
switched to using openssl, so going back to figure out what's wrong<br>
with gnutls has never been a high priority. If you switch you should<br>
test carefully, but from my experience openssl works better.<br>
<span class=""><br>
> This is why the package config settins are present in the curl recipe. You can<br>
> adjust the setting to use whatever TLS engine you want in your distribution or<br>
> project configuration.<br>
><br>
> PACKAGECONFIG_pn-curl = "ipv6 proxy ssl threaded-resolver zlib"<br>
<br>
</span>This will work, but a more robust approach may be to use _append and<br>
_remove to change PACKAGECONFIG options (rather than over-riding with<br>
an absolute set of options, which may become out of sync with the<br>
defaults in the main recipe). e.g.<br>
<br>
PACKAGECONFIG_remove_pn-curl = "gnutls"<br>
PACKAGECONFIG_append_pn-curl = " ssl"<br>
<div class="HOEnZb"><div class="h5"><br>
> or any other combination of available options..<br>
><br>
> --Mark<br>
><br>
>> Regards,<br>
>><br>
>> 2018-05-07 15:59 GMT+03:00 Alexander Kanavin <<a href="mailto:alexander.kanavin@linux.intel.com">alexander.kanavin@linux.<wbr>intel.com</a><br>
>> <mailto:<a href="mailto:alexander.kanavin@linux.intel.com">alexander.kanavin@<wbr>linux.intel.com</a>>>:<br>
>><br>
>> On 05/07/2018 03:51 PM, Viacheslav Salnikov wrote:<br>
>><br>
>> cULR is built with GNUTLS for Target but OpenSSL is used for native and SDK.<br>
>><br>
>> So my question is: why GNUTLS is used only for target? Is it necessary<br>
>> for some good reason? Documentation for cURL has no explicit answer for<br>
>> that.<br>
>><br>
>> Could somebody help me to find the answer?<br>
>><br>
>><br>
>> I think enabling gnutls on the native side would add a ton of dependencies<br>
>> to build, and so openssl (which is more self-contained) is selected there.<br>
>><br>
>> Alex<br>
>><br>
>><br>
>><br>
>><br>
><br>
</div></div><span class="HOEnZb"><font color="#888888">> --<br>
> ______________________________<wbr>_________________<br>
> Openembedded-core mailing list<br>
> <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</font></span></blockquote></div><br></div>