Hi, On Sun, May 27, 2012 at 10:43:39AM +0200, Mathieu Malaterre wrote: > Hi there, ... > > CCed: Bill who is libjpeg maintainer. > > As far as I know libjpeg is not really concerned here. virtualgl only > links to libturbojpeg. So there really are two issues in a single > report: > 1. optimized jpeg lib, as a replacement for libjpeg8 > 2. getting bumblebeed/virtualgl/turbojpeg(only) in debian > > Maybe it would be easier to only focus on (2) ?
YES. If you are more capable than me, you can copy required sources to virtualgl via debian/* and build it without requiring non-exisiong packahes. Do you have patch to address this in a short notice? For a person like me with less capability, uploads this package to provide required packages seems to be the easiest thing to do. build-depens on static library is not so complicated for binary image. I know it is not so useful for most wheesy system but this is useful in chroot. > Does libjpeg-turbo8 implement the full v8 API ? As far as I understand > some functions are stub. I do not know. For now, we only nned -dev package for building package with static library and *.h files. Fow wheesy, no one here, I expect to remove old libjpeg8. We just need to build virtualgl. Regards, Osamu -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120527163358.GA21271@localhost
