> Actually, the *only* thing I do with jpeg is decompress the image, > I don't really use any fltk-jpeg related things. By the time the > stupid little image gets there, it's just an array of chars > suitable for > an RGB image.
And that is all the functionality that we provide in the fltk built-in jpeg support, which really is just a bundled copy of jpeg6b. It is also exactly *why* we provide the built-in jpeg support, so that users of fltk can reliably and consistently handle the reading of jpeg image files, without concern as to what the target platform or distro happens to have installed. I honestly think that configuring your fltk lib with --enable-local-jpeg set, and then linking statically to libfltk_jpeg.a will resolve pretty much all the issues. > But you see, this sort of finger pointing is precisely why I took the > silly-looking route of doing the decompression in my own separate > namespace. Which is what the fltk built-in libjepg is for, so it may be that you are duplicating work that was already done? > You say fedora folks do stupid things, perhaps they do. No, I don't say they do stupid things, I said they follow the cutting edge, and that is their stated objective, and the specific mandate that distinguishes the fedora releases from the more conservative Red Hat releases, or indeed debian. However, I am concerned that this policy can be disruptive, and a lot of people trip up over this, (it seems to me that a lot of people install fedora without realising that it is a distro whose specific intent is to push the envelope in this way) and it creates breakage elsewhere in the software ecosystem that, from time to time, we are left to tidy up. > Fedora people will say you do stupid things. I doubt they even know I exist... ;-) On a more serious note, there's not much evidence that fedora are all that interested in fltk, so if their latest revisions have introduced some breakage, I doubt they have noticed, and probably will not unless someone files a bug. Conversely, since I no longer track the fedora releases, I didn't know that fltk was broken by their changes. If you have specific examples where replacing jpeg6b with jpeg7 has caused breakage, the fedora folk would probably be grateful of the bug reports, because that is exactly the sort of thing they are setting out to find and fix (so that it doesn't lead to breakage in Red Hat down the line...) And on the flip side - if you have notes on what failed in fltk linking against jpeg7, can you please file an STR so that we can investigate? We have to assume that whatever breakage we get from jpeg7 will only be a precursor to what happens if/when jpeg8 ever comes out. SELEX Sensors and Airborne Systems Limited 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
