VirtualGL uses the TurboJPEG API, not the libjpeg API, so it's not a matter of making VirtualGL use libjpeg. It's a matter of producing a TurboJPEG wrapper for libjpeg. The TurboJPEG code (turbojpeg.c in the libjpeg-turbo source) supports being built against plain libjpeg rather than libjpeg-turbo. If it detects that it isn't being built against libjpeg-turbo, then it will include (rather slow) code to emulate the libjpeg-turbo colorspace extensions. Thus, whoever is packaging things for your O/S would need to include two different TurboJPEG implementations-- one for libjpeg-turbo and the other for libjpeg.
Again, I know nothing of Gentoo. I've never even booted it. I have no idea how those packages work or who is producing them. I can only support the binary packages that are produced through this project. On 3/20/14 5:47 AM, Andreas Grapentin wrote: > Greetings, > > Okay, let me rephrase my question a bit :) > Would it be feasable for virtualgl in general to use either > libjpeg-turbo or libjpeg, depending on which is available on the host > system? > > I have looked into the package a bit, and on first glance it seems to be > ... complicated. > > Thanks, > Andreas ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
