public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: jpeg package: wrong jpeglib.h?
Date: Wed, 03 Sep 2003 05:11:00 -0000	[thread overview]
Message-ID: <3F55775D.1060200@cwilson.fastmail.fm> (raw)
In-Reply-To: <3F550950.D79C6FDC@quicknet.nl>

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/

      reply	other threads:[~2003-09-03  5:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  0:13 Teun Burgers
2003-09-03  5:11 ` Charles Wilson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F55775D.1060200@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).