From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] libv4l: Bump version to 1.0.1
Date: Sun, 29 Jun 2014 00:50:19 -0300 [thread overview]
Message-ID: <20140629035019.GA820@arch.cereza> (raw)
In-Reply-To: <20140628235847.0396216d@free-electrons.com>
On 28 Jun 11:58 PM, Thomas Petazzoni wrote:
[..]
>
> Thanks, the patch looks good in principle, but unfortunately it doesn't
> apply on the latest master, due to conflicts in libv4l.mk. Can you
> respin on top of the latest master and resend?
Ouch, my bad. I forgot to rebase my local branch on top of latest master.
> I think you can get rid
> of the [RFC] tag as well, I don't think there's anything really
> controversial or requiring discussion here.
>
OK, no problem.
> > -config BR2_PACKAGE_LIBV4L_DECODE_TM6000
> > - bool "decode_tm6000"
> > - depends on BR2_TOOLCHAIN_USES_GLIBC
> > +config BR2_PACKAGE_LIBV4L_UTILS
> > + bool "v4l-utils tools"
> > help
> > - Tool to decode tm6000 proprietary format streams
> > -
> > -comment "decode_tm6000 needs an (e)glibc toolchain"
> > - depends on !BR2_TOOLCHAIN_USES_GLIBC
> > -
> > -config BR2_PACKAGE_LIBV4L_IR_KEYTABLE
> > - bool "ir-keytable"
> > - depends on BR2_TOOLCHAIN_USES_GLIBC
> > - help
> > - Tool to alter keymaps of Remote Controller devices
> > -
> > -comment "ir-keytable needs an (e)glibc toolchain"
> > - depends on !BR2_TOOLCHAIN_USES_GLIBC
> > -
> > -config BR2_PACKAGE_LIBV4L_V4L2_COMPLIANCE
> > - bool "v4l2-compliance"
> > - depends on BR2_INSTALL_LIBSTDCPP
> > - help
> > - Tool to test v4l2 API compliance of drivers
> > -
> > -comment "v4l2-compliance needs a toolchain w/ C++"
> > - depends on !BR2_INSTALL_LIBSTDCPP
> > -
> > -config BR2_PACKAGE_LIBV4L_V4L2_CTL
> > - bool "v4l2-ctl"
> > - depends on BR2_INSTALL_LIBSTDCPP
>
> Can you make sure that the programs do not need C++ support, since
> you're getting rid of the dependency entirely?
>
Yes, I will.
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
prev parent reply other threads:[~2014-06-29 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 13:56 [Buildroot] [RFC] libv4l: Bump version to 1.0.1 Ezequiel Garcia
2014-06-28 21:58 ` Thomas Petazzoni
2014-06-29 3:50 ` 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=20140629035019.GA820@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