From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/1] package/libcurl: introduce options to reduce feature set
Date: Thu, 07 Feb 2019 22:41:08 +0100 [thread overview]
Message-ID: <87mun71dl7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190207205510.11172-1-patrickdepinguin@gmail.com> (Thomas De Schampheleire's message of "Thu, 7 Feb 2019 21:55:09 +0100")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
> From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> Libcurl is more than 250 KiB (libcurl) / 100 KiB (curl binary) in size.
> About 50 KiB / 15 KiB of this can be saved by disabling features/protocols
> that are not commonly needed:
> - proxy support: 15 KiB
> - cookies support: 10 KiB
> - various less common protocols: 25 KiB (libcurl) + 15 KiB (curl binary)
> Note that the exact amount of space saved depends on the architecture,
> toolchain, and other factors (for example the 'reduced' set disables the
> --libcurl option which only has impact on the curl binary).
> Other packages that are selecting libcurl could be incompatible with these
> reduced options. But, there is no clear way to find out which packages are in
> this situation, in particular because issues may only be visible at runtime.
That is not really nice :/
> +config BR2_PACKAGE_LIBCURL_SMALL
> + bool "reduced protocol/feature selection"
I know I proposed this option myself, but having a negative option like
this is not really nice. What should a package that needs libcurl built
without the _SMALL option do? Depending on !BR2_PACKAGE_LIBCURL_SMALL
isn't really nice.
Could we perhaps invert the option and call it BR2_PACKAGE_LIBCURL_EXTRA or
something like that? (with default y)
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-02-07 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 20:55 [Buildroot] [PATCHv2 1/1] package/libcurl: introduce options to reduce feature set Thomas De Schampheleire
2019-02-07 21:41 ` Peter Korsgaard [this message]
2019-02-08 21:25 ` Thomas De Schampheleire
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=87mun71dl7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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