From: Martin Jansa <martin.jansa@gmail.com>
To: nitin.a.kamble@intel.com
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] gst-meta-base: bring in the v4l2 related gst plugin
Date: Fri, 9 Aug 2013 00:37:07 +0200 [thread overview]
Message-ID: <20130808223707.GA17945@jama> (raw)
In-Reply-To: <ebd74052582cd3def1b5a4c3d609cfc6b2613933.1375996888.git.nitin.a.kamble@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
On Thu, Aug 08, 2013 at 09:34:29PM +0000, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> If the v4l2 machine feature is enabled, then the v4l2 gstreamer plugin
> is also pulled in the gst-meta-base packages.
>
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb b/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb
> index 210da37..c1139f4 100644
> --- a/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb
> +++ b/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb
> @@ -35,7 +35,9 @@ RDEPENDS_gst-meta-base = "\
> gst-plugins-base-videoscale \
> gst-plugins-base-ffmpegcolorspace \
> gst-plugins-good-autodetect \
> - gst-plugins-good-souphttpsrc"
> + gst-plugins-good-souphttpsrc \
> + gst-plugins-base-videotestsrc \
> + ${@base_contains('MACHINE_FEATURES', 'v4l2', 'gst-plugins-good-video4linux2', '', d)}"
I was expecting to see PACKAGECONFIG somewhere, is v4l2 autodetected?
Why not keep v4l2-utils in meta-multimedia?
>
> RRECOMMENDS_gst-meta-x11-base = "\
> gst-plugins-base-ximagesink \
> --
> 1.8.1.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-08-08 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 21:34 [PATCH 0/3] RFC: few commits for a new machine feature: v4l2 nitin.a.kamble
2013-08-08 21:34 ` [PATCH 1/3] v4l-utils: a new recipe nitin.a.kamble
2013-08-08 21:34 ` [PATCH 2/3] packagegroup-base.bb: add a new machine feature: v4l2 nitin.a.kamble
2013-08-08 21:34 ` [PATCH 3/3] gst-meta-base: bring in the v4l2 related gst plugin nitin.a.kamble
2013-08-08 21:57 ` Otavio Salvador
2013-08-08 22:00 ` Kamble, Nitin A
2013-08-08 22:37 ` Martin Jansa [this message]
2013-08-08 23:10 ` Kamble, Nitin A
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=20130808223707.GA17945@jama \
--to=martin.jansa@gmail.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=nitin.a.kamble@intel.com \
/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