[OE-core] [RFC] Use libjpeg-turbo in place of libjpeg

[Martin Jansa]

On Fri, Nov 27, 2015 at 09:13:22AM -0200, Otavio Salvador wrote:
> On Fri, Nov 27, 2015 at 9:04 AM, Maxin B. John <maxin.john at intel.com> wrote:
> > 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.
> 
> I support this change, due:
> 
>  - agreement with major Linux distros
>  - performance improvement
> 
> I also think moving libjpeg (API version 9) for meta-oe is fine as
> well. I am not aware of any application which requires it, though.

I'm not aware of any as well, so I would prefer to drop libjpeg
completely.

+ less junk in meta-oe
+ people were confused about multiple jpeg providers before, now they
would be again, but without good reason (as nobody knows about apps
depending on libjpeg9).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20151127/da501caa/attachment-0002.sig>