It seems most of the major Linux distributions have moved from libjpeg over to libjpeg-turbo, and not just for performance reasons. http://www.libjpeg-turbo.org/Main/HomePage There's a lengthy discussion over on the Debian mailing lists where they discussed their own move: http://debian.2.n7.nabble.com/jpeg8-vs-jpeg-turbo-tt2921094.html It may be about time for us to make this move ourselves. meta-oe has been maintaining a libjpeg-turbo recipe for some time now which could easily be pulled in to replace our existing libjpeg recipe.
+1, this is something I've been meaning to suggest. One thing to note though: we currently have libjpeg 9a. This may have been a mistake in the first place but it's something we have to take into account. My understanding of the situation: * distros are largely on API version 6 (I believe both Fedora and Debian) * jpeg-turbo can support 6 or 8 * jpeg-turbo does not support 9 and never will (and we probably shouldn't do that either by default) http://www.libjpeg-turbo.org/About/Jpeg-9 So if we move to jpeg-turbo, it seems we will "break" API. The question is, should we default to APIv6 like others or continue with 8 which would be closest to the current 9? This probably warrants a mailing list thread after release. Alex: does webkit support both or just APIv8?
That is a good point. As you suggest I think the best course would be to put it out to the community on the mailing list and see what people think.
I never investigated that, I simply updated jpeg together with webkit. Someone needs to swap one for the other and see what breaks.
I suspect nothing will, but of course we won't know for sure until it's tested.
Sent RFC patch to oe-core: http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113459.html
patch sent to oe-core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113516.html
Accepted upstream: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ffa746946f830c8161e43a151df7cd942bce63f3
Verified on master: 7a700f59d98ffe08714582532d3edb97abc2e33e Steps: 1. $ bitbake -s | grep libjpeg libjpeg-turbo :8d+1.4.2-r0 libjpeg-turbo-native :8d+1.4.2-r0 No libjpeg recipe found, only libjpeg-turbo.