From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] Import libav from meta-oe
Date: Fri, 9 Aug 2013 09:59:29 +0100 [thread overview]
Message-ID: <cover.1376038140.git.paul.eggleton@linux.intel.com> (raw)
Bring in the libav (ffmpeg replacement) recipe from meta-oe. Motivations
behind this:
* Enhances the performance/capability of gst-ffmpeg (which we already
have in OE-Core) by switching it to use an up-to-date version of libav
instead of the old internal copy of ffmpeg
* Allows dropping the gst-ffmpeg bbappend from meta-oe which does the above
* Provides a standard libav recipe to prevent ffmpeg/libav needing to be
added by other layers
A number of improvements to the recipes themselves have been made in the
process, see individual changes for details. Note that these recipes are
protected by LICENSE_FLAGS = "commercial".
The following changes since commit 291ab168fac15eae0e4c9234e16f394b0e1547a0:
subversion: Add patch to use neon 0.30 (2013-08-07 07:43:31 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/libav
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/libav
Paul Eggleton (6):
yasm: add from meta-oe and tweak
x264: add from meta-oe, update and tweak
libav: add from meta-oe, update and tweak
gst-ffmpeg: merge in bbappend from meta-oe
gst-ffmpeg: enable using yasm during build
gst-ffmpeg: set SUMMARY instead of DESCRIPTION
meta/recipes-devtools/yasm/yasm_1.2.0.bb | 13 +++
.../gstreamer/gst-ffmpeg_0.10.13.bb | 12 +-
.../0001-configure-enable-pic-for-AArch64.patch | 23 ++++
meta/recipes-multimedia/libav/libav.inc | 129 +++++++++++++++++++++
meta/recipes-multimedia/libav/libav_0.8.8.bb | 18 +++
meta/recipes-multimedia/libav/libav_git.bb | 16 +++
.../don-t-default-to-cortex-a9-with-neon.patch | 20 ++++
meta/recipes-multimedia/x264/x264_git.bb | 52 +++++++++
8 files changed, 277 insertions(+), 6 deletions(-)
create mode 100644 meta/recipes-devtools/yasm/yasm_1.2.0.bb
create mode 100644 meta/recipes-multimedia/libav/libav-0.8.8/0001-configure-enable-pic-for-AArch64.patch
create mode 100644 meta/recipes-multimedia/libav/libav.inc
create mode 100644 meta/recipes-multimedia/libav/libav_0.8.8.bb
create mode 100644 meta/recipes-multimedia/libav/libav_git.bb
create mode 100644 meta/recipes-multimedia/x264/x264/don-t-default-to-cortex-a9-with-neon.patch
create mode 100644 meta/recipes-multimedia/x264/x264_git.bb
--
1.8.1.2
next reply other threads:[~2013-08-09 8:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 8:59 Paul Eggleton [this message]
2013-08-09 8:59 ` [PATCH 1/6] yasm: add from meta-oe and tweak Paul Eggleton
2013-08-09 16:32 ` Burton, Ross
2013-08-09 16:37 ` Paul Eggleton
2013-08-09 8:59 ` [PATCH 2/6] x264: add from meta-oe, update " Paul Eggleton
2013-08-09 9:20 ` Martin Jansa
2013-08-09 9:58 ` Paul Eggleton
2013-08-09 8:59 ` [PATCH 3/6] libav: " Paul Eggleton
2013-08-14 12:22 ` Martin Jansa
2013-08-14 13:07 ` Phil Blundell
2013-08-14 13:57 ` Burton, Ross
2013-08-09 8:59 ` [PATCH 4/6] gst-ffmpeg: merge in bbappend from meta-oe Paul Eggleton
2013-08-09 8:59 ` [PATCH 5/6] gst-ffmpeg: enable using yasm during build Paul Eggleton
2013-08-09 8:59 ` [PATCH 6/6] gst-ffmpeg: set SUMMARY instead of DESCRIPTION Paul Eggleton
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=cover.1376038140.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.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