From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] wolfssl: new package
Date: Sat, 30 Dec 2017 21:35:28 +0100 [thread overview]
Message-ID: <20171230213528.75330a5b@windsurf> (raw)
In-Reply-To: <1514046735-14732-1-git-send-email-sergio.prado@e-labworks.com>
Hello,
On Sat, 23 Dec 2017 14:32:15 -0200, Sergio Prado wrote:
> The wolfSSL embedded SSL library is a lightweight and portable
> SSL/TLS library.
>
> Tested on Beaglebone Black using a tool called testsuite that
> comes with wolfssl source code inside the testsuite/ directory.
> To build it, we have to pass --enable-examples in the configure,
> and then manually copy the binary to the rootfs. Also, to use
> this tool, you will we need to copy the certs/* directory to the
> rootfs.
>
> Build-tested with test-pkg script.
>
> Signed-off-by: Sergio Prado <sergio.prado@e-labworks.com>
> ---
> Changes v1 -> v2:
> - bump to version 3.13.0
> - new version needs a toolchain with threads support
> - added two new menu options to enable all wolfssl features
> and SSv3 support
> - added an explanation on why we need autoreconf
> - removed options related to nginx, wpa_supplicant and lighttpd
> ---
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> package/wolfssl/Config.in | 27 +++++++++++++++++++++++++++
> package/wolfssl/wolfssl.hash | 6 ++++++
> package/wolfssl/wolfssl.mk | 38 ++++++++++++++++++++++++++++++++++++++
> 5 files changed, 73 insertions(+)
> create mode 100644 package/wolfssl/Config.in
> create mode 100644 package/wolfssl/wolfssl.hash
> create mode 100644 package/wolfssl/wolfssl.mk
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-12-30 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 16:32 [Buildroot] [PATCH v2] wolfssl: new package Sergio Prado
2017-12-30 20:35 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171230213528.75330a5b@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox