From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC] Use libjpeg-turbo in place of libjpeg
Date: Fri, 27 Nov 2015 13:04:17 +0200 [thread overview]
Message-ID: <1448622259-5907-1-git-send-email-maxin.john@intel.com> (raw)
This patch set provides libjpeg-turbo as a drop-in replacement for libjpeg.
libjpeg-turbo is a fork of the original libjpeg project.Most of the major Linux
distros (Fedora, Debian, OpenSUSE) moved from libjpeg to libjpeg-turbo recently.
lbjpeg-turbo provides better JPEG compression/decompression(at least 25% faster)
while maintaining same API/ABI as libjpeg.
Once we reach an agreement on this, based on the decision, we can move the
libjpeg package to meta-oe for applications which may depend on API version 9.
[YOCTO #8628]
Maxin B. John (2):
libjpeg: Replace libjpeg with libjpeg-turbo
libjpeg-turbo: import the recipe from meta-oe
meta/recipes-core/jpeg/jpeg_9a.bb | 29 -----------------
meta/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb | 40 ++++++++++++++++++++++++
2 files changed, 40 insertions(+), 29 deletions(-)
delete mode 100644 meta/recipes-core/jpeg/jpeg_9a.bb
create mode 100644 meta/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb
--
2.4.0
next reply other threads:[~2015-11-27 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 11:04 Maxin B. John [this message]
2015-11-27 11:04 ` [PATCH 1/2] libjpeg: Replace libjpeg with libjpeg-turbo Maxin B. John
2015-11-27 11:04 ` [PATCH 2/2] libjpeg-turbo: import the recipe from meta-oe Maxin B. John
2015-11-27 11:14 ` Martin Jansa
2015-11-27 12:20 ` Maxin B. John
2015-11-27 11:43 ` Jussi Kukkonen
2015-11-27 19:51 ` Andre McCurdy
2015-11-27 11:13 ` [RFC] Use libjpeg-turbo in place of libjpeg Otavio Salvador
2015-11-27 11:19 ` Martin Jansa
2015-11-27 11:21 ` Otavio Salvador
2015-11-27 12:22 ` Maxin B. John
2015-11-27 13:54 ` Mike Looijmans
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=1448622259-5907-1-git-send-email-maxin.john@intel.com \
--to=maxin.john@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 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.