From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gst1-plugins-bad: hls: allow user to select crypto backend
Date: Wed, 3 Aug 2016 14:29:25 +0200 [thread overview]
Message-ID: <20160803142925.3af9c6b7@free-electrons.com> (raw)
In-Reply-To: <1470226767-21018-1-git-send-email-rahul.bedarkar@imgtec.com>
Hello,
On Wed, 3 Aug 2016 17:49:27 +0530, Rahul Bedarkar wrote:
> +if BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_HLS
> +
> +choice
> + prompt "choose HLS cryptographic backend"
> + default BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_HLS_BACKEND_NETTLE
> +
> +config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_HLS_BACKEND_LIBGCRYPT
> + bool "libgcrypt"
> + depends on BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS # libgcrypt -> libgpg-error
> + select BR2_PACKAGE_LIBGCRYPT
> +
> +config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_HLS_BACKEND_NETTLE
> + bool "nettle"
> + select BR2_PACKAGE_NETTLE
> +
> +config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_HLS_BACKEND_OPENSSL
> + bool "openssl"
> + select BR2_PACKAGE_OPENSSL
> +
> +endchoice
I'm not sure I want to see a choice for this. Could we instead have
the .mk file automatically selected the backend according to which
crypto package(s) are available?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-03 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 12:19 [Buildroot] [PATCH 1/1] gst1-plugins-bad: hls: allow user to select crypto backend Rahul Bedarkar
2016-08-03 12:29 ` Thomas Petazzoni [this message]
2016-08-03 13:47 ` Rahul Bedarkar
2016-08-03 20:35 ` Peter Korsgaard
2016-08-04 10:09 ` Rahul Bedarkar
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=20160803142925.3af9c6b7@free-electrons.com \
--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