From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Alexander Shashkevych <alex@stunpix.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-demos][PATCH v2] packagegroup-fslc-gstreamer1.0-commercial: remove commercial recipe
Date: Thu, 27 Nov 2014 13:45:27 +0100 [thread overview]
Message-ID: <54771CE7.1040208@pseudoterminal.org> (raw)
In-Reply-To: <CAE6DSAHFvMpK-YjJ9J2x8HtZhJG=s2fAPpuf+u5zLa58bF85dQ@mail.gmail.com>
On 2014-11-27 13:41, Alexander Shashkevych wrote:
> On Wed, Nov 26, 2014 at 12:23 AM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> Sorry, typo. I meant "gstreamer1.0-plugins-ugly-asf" , not
>> "gstreamer1.0-plugins-ugly-asfdemux". The -asf package contains the
>> libgstasf.so plugin, which in turn contains the asfdemux element.
>>
> Could you point me on gstreamer1.0-plugins-ugly-asf package in layers?
> I have tried to search across poky/oe layers again, but have not found
> it.
>
I built the most recent state of the dizzy branch of poky and
meta-fsl-arm. I built "gstreamer1.0-plugins-ugly" with bitbake, and got
this file in tmp/deploy/ipk/cortexa9hf-vfp-neon/ :
gstreamer1.0-plugins-ugly-asf_1.4.1-r0_cortexa9hf-vfp-neon.ipk
Note that gstreamer1.0-plugins-ugly won't build unless "commercial is
added to LICENSE_FLAGS_WHITELIST. I add it in local.conf.
next prev parent reply other threads:[~2014-11-27 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 16:58 [meta-fsl-demos][PATCH v2] packagegroup-fslc-gstreamer1.0-commercial: remove commercial recipe Alexander Shashkevych
2014-11-25 22:22 ` Carlos Rafael Giani
2014-11-25 22:23 ` Carlos Rafael Giani
2014-11-26 8:59 ` Alexander Shashkevych
2014-11-27 12:41 ` Alexander Shashkevych
2014-11-27 12:45 ` Carlos Rafael Giani [this message]
2014-11-27 14:20 ` Alexander Shashkevych
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=54771CE7.1040208@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=alex@stunpix.com \
--cc=meta-freescale@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.