Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Enabling x264 support in gstreamer
Date: Tue, 13 Aug 2013 20:45:16 +0100	[thread overview]
Message-ID: <2166743.qly9touZmz@helios> (raw)
In-Reply-To: <520A6ECF.8000002@windriver.com>

On Tuesday 13 August 2013 12:37:19 Mark Hatle wrote:
> On 8/13/13 12:29 PM, Gary Thomas wrote:
> > I see that some of the gstreamer recipes have changed so that x264
> > is now a PACKAGECONFIG option.  However, I don't see anything that
> > enables this option anywhere.
> > 
> > How do I get x264 support back - it was working with Poky/Yocto
> > just a few weeks back...
> > 
> > Note: I have imported meta-oe/recipes-multimedia/x264 from
> > meta-openembedded into my layers for this [library] package.
> 
> I havn't worked with this myself, but my guess is.  In your
> distribution.conf file (or your local.conf):
> 
> PACKAGECONFIG_gst-plugins-ugly = "x264"
> 
> or
> 
> PACKAGECONFIG_gstreamer1.0-plugins-ugly = "a52dec lame mad mpeg2dec x264"

You missed out the "pn-" which is necessary for such per-recipe overrides to 
work. The correct examples would be:

PACKAGECONFIG_pn-gst-plugins-ugly = "x264"
 
or

PACKAGECONFIG_pn-gstreamer1.0-plugins-ugly = "a52dec lame mad mpeg2dec x264"

If preferred you could use ..._append_pn-... = " x264" to add to the existing 
options rather than setting them outright.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-08-13 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 17:29 Enabling x264 support in gstreamer Gary Thomas
2013-08-13 17:36 ` Martin Jansa
2013-08-13 19:26   ` Gary Thomas
2013-08-13 19:36     ` Phil Blundell
2013-08-13 19:42       ` Paul Eggleton
2013-08-13 20:09       ` Martin Jansa
2013-08-13 17:37 ` Mark Hatle
2013-08-13 19:45   ` Paul Eggleton [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=2166743.qly9touZmz@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=mark.hatle@windriver.com \
    --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