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

[Otavio Salvador]

On Fri, Nov 27, 2015 at 9:19 AM, Martin Jansa <martin.jansa at gmail.com> wrote:
> 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).

Agreed.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750