Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3F55775D.1060200@cwilson.fastmail.fm> Date: Wed, 03 Sep 2003 01:08:45 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: jpeg package: wrong jpeglib.h? References: <3F550950 DOT D79C6FDC AT quicknet DOT nl> In-Reply-To: <3F550950.D79C6FDC@quicknet.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Teun Burgers wrote: > I've got a program that won't compile with /usr/include/jpeglib.h. > The reason is that struct jpeg_component_info does > not contain height_in_blocks. > > The jpeglib.h distributed in jpegsrc.v6b.tar.gz from > http://www.ijg.org/files/ *does* contains height_in_blocks. > > What is the reason for using a different jpeglib.h? Cygwin's jpeg is built with the lossless jpeg patch, which modifies the header files slightly. However, if you read the header file carefully, height_in_blocks is in the PRIVATE section of the header. It is NOT supposed to be accessed by external programs -- I have this on the highest (for jpeg) authority, Tom Lane himself. So, don't do that. But, if you must do that, height_in_blocks has simply been renamed to "height_in_data_units" -- because with lossless jpeg, each "compression unit" is not necessarily a DCT block. Please search the mailing list archives where this has been discussed in the past. IIRC several mechanisms for working transparently with the cygwin versions of the jpeglib headers were presented in those discussions. -- Chuck -- 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/