From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnutls: use included unistring unless libunistring is selected
Date: Sun, 17 Jun 2018 14:17:21 +0200 [thread overview]
Message-ID: <20180617141721.6b5dcc95@windsurf> (raw)
In-Reply-To: <20180615084838.7642-1-neumann@teufel.de>
Hello,
On Fri, 15 Jun 2018 10:48:38 +0200, Sven Neumann wrote:
> Use the included copy of libunistring unless BR2_PACKAGE_LIBUNISTRING
> is already selected.
>
> The resulting gnutls library with libunistring included is about 1.2 MB
> smaller than the sum of libgnutls and libunistring.
>
> Signed-off-by: Sven Neumann <neumann@teufel.de>
> ---
> package/gnutls/Config.in | 1 -
> package/gnutls/gnutls.mk | 10 ++++++++--
> 2 files changed, 8 insertions(+), 3 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-06-17 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 8:48 [Buildroot] [PATCH] gnutls: use included unistring unless libunistring is selected Sven Neumann
2018-06-15 8:57 ` Baruch Siach
2018-06-17 12:24 ` Thomas Petazzoni
2018-06-17 12:17 ` 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=20180617141721.6b5dcc95@windsurf \
--to=thomas.petazzoni@bootlin.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