Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gst1-plugins-bad: hls: fix broken dependency
Date: Fri, 5 Aug 2016 21:11:28 +0200	[thread overview]
Message-ID: <20160805211128.0b02eda7@free-electrons.com> (raw)
In-Reply-To: <1470305203-1738-1-git-send-email-rahul.bedarkar@imgtec.com>

Hello,

On Thu, 4 Aug 2016 15:36:43 +0530, Rahul Bedarkar wrote:
> HLS plugin can be built with nettle or libgcrypt or openssl
> cryptographic backend. But current dependency on gnutls is incorrect.
> It has been working so far because gnutls depends on nettle.
> 
> gst-plugins-bad's build system for HLS allows user to choose which
> cryptographic backend to use. If that is not specified, it internally
> checks for nettle or libgcrypt or openssl in order. If none of the
> cryptographic backend is available, HLS plugin gets disabled internally.
> 
> Select cryptographic backend according to which cryptographic packages
> are available. If both libgcrypt or openssl are not available, choose
> nettle by default.
> 
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Reviewed-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>
> Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
> ---
>  package/gstreamer1/gst1-plugins-bad/Config.in           |  2 +-
>  package/gstreamer1/gst1-plugins-bad/gst1-plugins-bad.mk | 14 +++++++++++++-
>  2 files changed, 14 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-08-05 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 10:06 [Buildroot] [PATCH 1/1] gst1-plugins-bad: hls: fix broken dependency Rahul Bedarkar
2016-08-05 19:11 ` 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=20160805211128.0b02eda7@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