From: harshada <hgune@cisco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gstreamer not getting populated in file system
Date: Fri, 03 Dec 2010 12:09:11 +0530 [thread overview]
Message-ID: <4CF8908F.7030505@cisco.com> (raw)
In-Reply-To: <AANLkTimqLt1knQWUZiDEGs4H-kf=o-2o9vRkcwPU4pRZ@mail.gmail.com>
Hi Maksym,
Thanks for reply. I added a task called mytask as follows:
PACKAGES = "task-mytask"
RDEPENDS_task-mytask = " strace \
gstreamer \
gst-meta-base \
gst-plugins-base \
gst-plugins-good \
gst-plugins-bad \
gst-plugins-ugly "
DEPENDS_task-mytask = " "
RRECOMMENDS = " strace \
gstreamer \
gst-meta-base \
gst-plugins-base \
gst-plugins-good \
gst-plugins-bad \
gst-plugins-ugly "
And used it while creating image. But still I am not able to see the
gstreamer plugins populated.
I couldn't find any other meta bb file except gst-meta-base. What could
be the wrong?
~Harshada.
On Thursday 02 December 2010 02:56 PM, Maksym Parkachov wrote:
> Hi Harshada,
>
> I've seen the same behavior as you, instead of gst-plugins-base you
> need to use gst-plugins-base-meta, and correspondingly all other as
> well. During last couple of months gst-plugins-base, .etc. changed
> dependency on plugins from DEPENDS to RECOMMENDS.
>
> Hope this helps,
> Maksym.
>
> On Wed, Dec 1, 2010 at 5:40 PM, Tim Harvey<harvey.tim@gmail.com> wrote:
>
>> On 11/30/2010 12:26 AM, harshada wrote:
>>
>>> We created new image by adding following into minimal-image.bb:
>>> gstreamer \
>>> gst-plugins-base \
>>> gst-plugins-good \
>>> gst-plugins-bad \
>>> gst-plugins-ugly
>>> Image is getting built without any compiling issues. But we are not able
>>> to find required
>>> gstreamer plugins in the file system image. In ipk directory, we could
>>> find all of the corresponding ipks.
>>> What to do to get the filesystem populated with these gstreamer plugins?
>>>
>>> thanks and regards,
>>> Harshada
>>>
>> I believe you need to place the actual plugins in your image - do a find
>> tmp/deploy/ipk -name gst-plugin-*
>>
>> Tim
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
prev parent reply other threads:[~2010-12-03 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 8:26 gstreamer not getting populated in file system harshada
2010-12-01 16:40 ` Tim Harvey
2010-12-02 9:26 ` Maksym Parkachov
2010-12-03 6:39 ` harshada [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=4CF8908F.7030505@cisco.com \
--to=hgune@cisco.com \
--cc=openembedded-devel@lists.openembedded.org \
/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