8628 2015-11-02 17:21:31 +0000 Use libjpeg-turbo in place of libjpeg 2016-02-16 15:52:20 +0000 1 1 7 Build System, Metadata & Runtime OE-Core graphics 2.0 All Multiple VERIFIED FIXED Medium+ enhancement 2.1 M2 1 bluelightning maxin.john alex.kanavin alexandru.c.georgescu jku meta.mr.watcher meta.watcher daniel.alexandrux.istrate --- --- No (bug/feature does not impact docs) oldest_to_newest 56107 0 bluelightning 2015-11-02 17:21:31 +0000 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. 56126 1 jku 2015-11-03 08:51:49 +0000 +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? 56128 2 bluelightning 2015-11-03 09:34:41 +0000 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. 56133 3 alex.kanavin 2015-11-03 12:53:30 +0000 I never investigated that, I simply updated jpeg together with webkit. Someone needs to swap one for the other and see what breaks. 56134 4 bluelightning 2015-11-03 13:01:51 +0000 I suspect nothing will, but of course we won't know for sure until it's tested. 56856 5 maxin.john 2015-11-27 13:17:10 +0000 Sent RFC patch to oe-core: http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113459.html 56890 6 maxin.john 2015-12-01 12:58:54 +0000 patch sent to oe-core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113516.html 57619 7 maxin.john 2016-01-07 14:14:50 +0000 Accepted upstream: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ffa746946f830c8161e43a151df7cd942bce63f3 59109 8 daniel.alexandrux.istrate 2016-02-16 15:52:20 +0000 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.