> I say v7, but was not aware that there was v8 and v8a. I don't see > any useful documentation on http://www.ijg.org/ that seems to be the > official site, i.e. no release notes, no change log, ...
Yup - it is not the most verbose homepage... However, it currently says (grabbed right now from my browser): "The current version is release 8a of 28-Feb-2010. This is a stable and solid foundation for many application's JPEG support. You can find our code and some supporting documentation in the directory files. There is a Unix format package in tar.gz archive format jpegsrc.v8a.tar.gz and a Windows format package in zip archive format jpegsr8a.zip." So 8a is latest. If you then grab jpegsrc.v8a.tar.gz it contains a file "change.log" that clarifies things. A bit. Again, quoting from the v8a change.log file: "Add data source and destination managers for read from and write to memory buffers. New API functions jpeg_mem_src and jpeg_mem_dest." > I don't know. If we upgrade our bundled lib and use functions that > are available in v8x, then a user who configures to use the system > libs may get problems, unless we add more feature test macros to > autoconf and use this in our code. OTOH, if we could provide some > features like those you mentioned, this would probably be good. > > Maybe we should wait some time until v8 is more in use in Linux > distributions and elsewhere. I was mainly thinking that the bundled lib would be statically linked anyway, so ABI differences are a Don't Care. The API is not changed AFAIK. SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
