Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: ATTN: jpeglib maintainer Date: Fri, 22 Jul 2005 08:39:29 +0200 Message-ID: From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j6M7KcxG024282 Hi Chuck, Charles Wilson wrote on Friday, July 22, 2005 12:22 AM: [snip] > > So, what to do? On cygwin, I think you just need to do something > like this: > > #ifdef __CYGWIN__ > # define CHECK_PROGRESSIVE(cinfo) (cinfo->process == > JPROC_PROGRESSIVE) #else # define CHECK_PROGRESSIVE(cinfo) > (cinfo->progressive_mode) #endif > > and replace all accesses to progressive_mode with this macro. Thanks for explanation. Your suggested method works. > Note that you'll also need to do something similar for the > change: 'width_in_blocks' --> 'width_in_data_units' > 'height_in_blocks' --> 'height_in_data_units' But search the > archives for more information about these two beasties. > > There has been some movement in recent months on the jpeglib > mailing list about rolling out a jpeg-6c (and possibly a > jpeg-7). It is an open question whether that process may > eventually fold something like lossless jpeg into the main > codebase in a non-disruptive way. We'll just have to wait and see. :) - Jörg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/