From: Gary Thomas <gary@mlbassoc.com>
To: Tim Biernat <biernat@ieee.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: re. Enabling x264 support in gstreamer
Date: Mon, 16 Sep 2013 16:22:51 -0600 [thread overview]
Message-ID: <523784BB.8080404@mlbassoc.com> (raw)
In-Reply-To: <CAH2s=tsyyTMO9KoJMfP0SS4x0vMLphYuDWhPEv0eWeui3CjJ1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
On 2013-09-16 16:09, Tim Biernat wrote:
> Just wondering if you got this working? I am trying to build gstreamer with h.264 support on Intel n450 for some time now without success.
Firstly, since this message was on a public email list, it's polite
to keep the discussion there so that everyone benefits.
Also, not quoting any of the previous message makes it very difficult
to follow up - you can't imagine how many emails I've written since
that one which was a month ago...
I did indeed get it working by using the attached .bbappend file.
Actually pretty simple, I hope that the documentation on PACKAGECONFIG
catches up soon.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
[-- Attachment #2: gst-plugins-ugly_0.10.19.bbappend --]
[-- Type: text/plain, Size: 136 bytes --]
#
# Adjust desired plugins which are not in Poky/Yocto because of licensing requirements
#
DEPENDS += " x264 "
PACKAGECONFIG += "x264"
next parent reply other threads:[~2013-09-16 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH2s=tsyyTMO9KoJMfP0SS4x0vMLphYuDWhPEv0eWeui3CjJ1w@mail.gmail.com>
2013-09-16 22:22 ` Gary Thomas [this message]
2013-09-16 22:32 ` re. Enabling x264 support in gstreamer Burton, Ross
2013-09-17 10:59 ` Gary Thomas
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=523784BB.8080404@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=biernat@ieee.org \
--cc=openembedded-core@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