Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libv4l: Bump version to 1.0.1
Date: Tue, 1 Jul 2014 23:35:17 -0300	[thread overview]
Message-ID: <20140702023516.GB995@arch.cereza> (raw)
In-Reply-To: <20140701232648.33bc4483@free-electrons.com>

On 01 Jul 11:26 PM, Thomas Petazzoni wrote:
> On Sun, 29 Jun 2014 18:18:34 -0300, Ezequiel Garcia wrote:
> 
> > -config BR2_PACKAGE_LIBV4L_V4L2_CTL
> > -	bool "v4l2-ctl"
> > -	depends on BR2_INSTALL_LIBSTDCPP
> > +config BR2_PACKAGE_LIBV4L_JPEG
> > +	bool "JPEG support"
> 
> I think there needs to be a justification as to why we want a
> sub-option to enable jpeg support, as opposed to have it directly
> handled as an optional dependency in the .mk file by testing
> BR2_PACKAGE_JPEG.
> 

That could work, as long as we have a comment to show the dependency
in the menu. Otherwise, I don't like to "hide" this from a user wanting
to enable or disable this.

> > -comment "libv4l needs a toolchain w/ largefile, threads"
> > +comment "libv4l needs a toolchain w/ largefile, threads and C++"
> >  	depends on !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS
> > +	depends on !BR2_INSTALL_LIBSTDCPP
> 
> The main problem is here, you should use:
> 
> 	depends on !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP
> 
> Otherwise, the comment will not get displayed in the proper situations.
> 
> Can you fix that up and resend?
> 

No problem.

-- 
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar

      reply	other threads:[~2014-07-02  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 21:18 [Buildroot] [PATCH] libv4l: Bump version to 1.0.1 Ezequiel Garcia
2014-07-01 21:26 ` Thomas Petazzoni
2014-07-02  2:35   ` Ezequiel Garcia [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=20140702023516.GB995@arch.cereza \
    --to=ezequiel@vanguardiasur.com.ar \
    --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