From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RESEND PATCH v3 1/1] package/iputils: add configs to select which binaries are built
Date: Thu, 3 Sep 2020 21:49:41 +0200 [thread overview]
Message-ID: <20200903214941.536f6956@windsurf.home> (raw)
In-Reply-To: <4e8f64ec-1797-a418-79d7-701380a767db@gmail.com>
On Sun, 15 Sep 2019 12:05:46 +0200
Alejandro Gonz?lez <alejandro.gonzalez.correo@gmail.com> wrote:
> By default, the iputils build script might build binaries which are
> useless for certain applications, like tftpd or ninfod. Those binaries
> will add to the target filesystem size unless a post-build script removes
> them manually, which is cumbersome and doesn't shorten build times.
>
> In particular, in a certain aarch64 Buildroot project with musl selected
> as a C library, this patch allowed to shrink the full iputils package from
> 219 KiB (if every option is selected) to 63 KiB (with only the ping
> binary selected) - a 71.2% relative size decrease.
>
> Moreover, upstream recently introduced a commit that disabled tftpd from
> building by default, like rarpd. In the current state of things, this change
> will introduce inconveniences for Buildroot users which prefer to use the
> tftpd implementation provided by this package. With this patch, however, that
> decision and similar future ones won't be a concern, because they will
> have complete control of what binaries are built.
>
> These changes add Kconfig options which let the user select what
> binaries are built with ease.
>
> Signed-off-by: Alejandro Gonz?lez <alejandro.gonzalez.correo@gmail.com>
> ---
> Changes v2 -> v3:
> - Several style revisions (suggested by Arnout)
> - Simplify ninfod crypto dependencies logic (suggested by
> Arnout)
> - Better explain the rationale for this patch in the commit
> message
I have finally applied to master. The ninfod situation is now simpler
because iputils no longer needs any external crypto library.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-03 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 19:17 [Buildroot] [PATCH v3 1/1] package/iputils: add configs to select which binaries are built Alejandro González
2019-09-15 10:05 ` [Buildroot] [RESEND PATCH " Alejandro González
2019-09-15 12:23 ` Thomas Petazzoni
2020-09-03 19:49 ` Thomas Petazzoni [this message]
2020-09-08 13:33 ` Alejandro
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=20200903214941.536f6956@windsurf.home \
--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