Hi Saul, On Sep 6, 2012, at 4:14 PM, Saul Wold wrote:
> On 09/06/2012 02:59 PM, Chris Conlon wrote: >> Adding a direct link to the CyaSSL recipe file for review: >> >> www.yassl.com/files/yocto/cyassl_2.3.0.bb >> <http://www.yassl.com/files/yocto/cyassl_2.3.0.bb> >> > Chris, > > On initial inspection of this recipe it looks OK, what package/libraries does > it provide? Are they the same as the openssl package? It provides the CyaSSL embedded SSL library, specifically called "libcyassl". Although it offers similar functionality as the openssl package (SSL and crypto support), it shouldn't conflict naming wise. OpenSSL's library names are "libssl" and "libcrypto". > > You may need RCONFLICTS_${PN} and/or RPROVIDES_${PN}, where the ${PN} may > need to be the package names in openssl, I need to check that. CyaSSL shouldn't conflict with OpenSSL, as it has a different library name and header location. Thanks for the suggestion about RPROVIDES. I'm new to writing recipe files, so your feedback is very appreciated. > > I would suggest that initially you make this available as a standard > layer, possibly called meta-cyassl, it could be hosted on GitHub. You can add > it to the OpenEmbedded Layer Index. See > http://www.openembedded.org/wiki/LayerIndex > > Distributions that want to use this instead of OpenSSL can then use your > layer and select your recipe, if it's setup correctly it will provide what > they need. Ok, thanks for the pointer. Any chance of the recipe getting rolled into the OpenEmbedded/Yocto meta/recipes-connectivity layer? Thanks, Chris _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
