[Buildroot] [PATCH] wolfssl: new package
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Wed Dec 13 06:54:33 UTC 2017
Hello,
On Wed, 13 Dec 2017 08:03:08 +0200, Baruch Siach wrote:
> > It depends on the option, but in general enables some extra library
> > features that could be used by the specific application.
> >
> > For example, if you pass --enable-nginx, it will define OPENSSL_EXTRA that
> > will enable the wolfSSL OpenSSL compatibility layer to ease porting wolfSSL
> > into existing applications which had been designed to work with OpenSSL.
>
> So --enable-nginx is not nginx specific. It would probably make sense to
> enable it for other packages as well. What about the --enable-lighty and
> --enable-wpas options? How large is the target size increase of these options?
>
> In any case we need a comment that explains all that.
I also agree that the way it's done in the current proposal is very
confusing. I looked at the patch before looking at Baruch answer and
was about to make the exact same comment.
In addition, enabling those features currently doesn't make much sense,
because none of lighttpd, wpa_supplicant or nginx have an optional
dependency on wolfssl.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
More information about the buildroot
mailing list