I'll see what I can do, but I suspect that it's going to be very
complicate to #ifdef around the stuff I'm putting in. I don't really
understand why compatibility with the system libjpeg is important. Only
on Linux is there even a concept of a "system libjpeg."
If I understand it correctly, the main problem is that the libjpeg API
isn't enough for these performance enhancements? In that case, would it be
possible to extend the API of "our" libjpeg, and then also write
compatibility stubs that emulates the extended API upon a "system
libjpeg"?
I think that having a well-defined JPEG library API is important. For
example, people might eventually want to replace their normal libjpeg
library with our SIMD one. In that case it is of course important that the
API is compatible. It might also be useful to, for testing or other
purposes, replace our SIMD jpeg with something else, say a glue to IPP or
OpenMedialib. So having a well defined "border" seems very useful to me.
Best regards,
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
