All of lore.kernel.org
 help / color / mirror / Atom feed
From: "piotr.lewicki" <piotr.lewicki@elfin.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-multimedia] libav missing
Date: Wed, 20 Apr 2016 13:00:05 +0200	[thread overview]
Message-ID: <57176135.5040904@elfin.de> (raw)
In-Reply-To: <57175267.3020504@mlbassoc.com>

It is being used in recipe for "omxplayer".
I have already renamed "libav" to "ffmpeg". Once I'll test it (and fix 
other problems if they occur) I'll submit this simple patch.

Thanks,
Piotr

On 20.04.2016 11:56, Gary Thomas wrote:
> On 2016-04-20 11:50, piotr.lewicki wrote:
>> Hello,
>> I'm trying to build some image for raspberry pi and one of my 
>> dependencies is "libav".
>> Unfortunately it's missing from "meta-openembedded".
>> I found a commit which says that it has been moved to oe-core, but I 
>> have also cloned "openembedded-core" and there is
>> no "libav" either.
>> I'm using layers:
>> - meta-openembedded
>> - meta-raspberrypi
>> - openembedded-core
>> - poky
>> (all of them on master branches).
>>
>> Could you help me locate a recipe for libav?
>>
>
> libav in OE-core has been replaced by ffmpeg.
>
> What recipe are you missing libav for?
>
>> commit 30ba23377ec568a58c43e466582506980b67baad
>> Author: Paul Eggleton <paul.eggleton@linux.intel.com>
>> Date:   Tue Aug 13 22:30:03 2013 +0000
>>
>>      libav: remove
>>
>>      This is now in OE-Core.
>>
>>      Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
>>      Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>>
>
>



      reply	other threads:[~2016-04-20 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  9:50 [meta-multimedia] libav missing piotr.lewicki
2016-04-20  9:56 ` Gary Thomas
2016-04-20 11:00   ` piotr.lewicki [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=57176135.5040904@elfin.de \
    --to=piotr.lewicki@elfin.de \
    --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 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.