Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gstreamer/zbar-plugin: propagate dependencies from zbar
Date: Fri, 01 Jan 2016 19:55:16 +0100	[thread overview]
Message-ID: <87vb7druy3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1451673257-23081-1-git-send-email-romain.naour@gmail.com> (Romain Naour's message of "Fri, 1 Jan 2016 19:34:17 +0100")

>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:

 > BR2_PACKAGE_GST_PLUGINS_BAD_ZBAR select BR2_PACKAGE_ZBAR which
 > has several dependencies from libv4l.

 > Propagate these dependencies to avoid unmet dependencies while
 > selecting BR2_PACKAGE_GST_PLUGINS_BAD_ZBAR.

 > Signed-off-by: Romain Naour <romain.naour@gmail.com>
 > ---
 >  package/gstreamer/gst-plugins-bad/Config.in | 5 +++++
 >  1 file changed, 5 insertions(+)

 > diff --git a/package/gstreamer/gst-plugins-bad/Config.in b/package/gstreamer/gst-plugins-bad/Config.in
 > index e2a67f1..95acbaf 100644
 > --- a/package/gstreamer/gst-plugins-bad/Config.in
 > +++ b/package/gstreamer/gst-plugins-bad/Config.in
 > @@ -322,6 +322,11 @@ config BR2_PACKAGE_GST_PLUGINS_BAD_PLUGIN_VP8
 
 >  config BR2_PACKAGE_GST_PLUGINS_BAD_ZBAR
 >  	bool "zbar"
 > +	depends on BR2_TOOLCHAIN_HAS_THREADS # zbar-> libv4l
 > +	depends on BR2_USE_MMU # zbar-> libv4l
 > +	depends on !BR2_STATIC_LIBS # zbar-> libv4l
 > +	depends on BR2_INSTALL_LIBSTDCPP # zbar-> libv4l
 > +	depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0 # zbar-> libv4l

You forgot to copy over the comment to be displayed if these
dependencies aren't available.

Committed with that fixed, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2016-01-01 18:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01 18:34 [Buildroot] [PATCH] package/gstreamer/zbar-plugin: propagate dependencies from zbar Romain Naour
2016-01-01 18:55 ` Peter Korsgaard [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=87vb7druy3.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