>>jpg-turbo should be a drop-in replacement with the same api, right? so
>> maybe it's not quite the same after all in this case.
Yes - exactly..
libjpeg-turbo tells it is ABI version 6b, but in reality it has some
version 8 features implemented. This leads to a linker collision, since I
define the missing functions when the libjpeg header tells me it is less
than v8. However, I now just use a different function name and a define to
make sure we cannot experience collisions.
http://stackoverflow.com/questions/11070473/how-can-i-use-jpeg-mem-src-jpeg-mem-dest-in-libjpeg-turbo
Regards, Klaus Post
http://www.klauspost.com
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
