21.5 Windows jpeg patch

[Ron Isaacson]

Jerry James wrote:
> 
> On Dec 11, 2007 8:32 PM, Ron Isaacson <Ron.Isaacson at morganstanley.com> wrote:
> > Aidan Kehoe wrote:
> > > Okay, I don't actually see the problem locally, but the patch seems sensible
> > > enough and it doesn't break the build or anything of the sort, so I've gone
> > > ahead and committed it. What exactly are the versions of the various
> > > libraries that break for you?
> >
> > Here are all of the external libs I'm using -- each is a local build
> > from source:
> >
> >   xpm  -> 3.4k
> >   png  -> 1.2.8
> >   zlib -> 1.2.3
> >   jpeg -> 6b.3
> >   tiff -> 3.7.2
> >
> > I read that this can happen if there's a mismatch between the
> > build-time and runtime versions of libjpeg, although on Windows
> > everything is static, so that shouldn't be an issue, right?
> >
> > I can reproduce this using:
> >
> >   (glyph-image-instance
> >     (make-glyph [jpeg :file "c:/any/image.jpg"]))
> >
> > Without the patch, it always fails with the error message above.
> 
> Can you grab a DLL dependency analyzer [1] and see what it says
> about JPEG DLLs?

Didn't find any at all. None of the dll's had "jpeg" or anything like
it in the name. I did find imgutil.dll and imagehlp.dll from
c:\windows\system32, but that's it.

Would you expect anything different? I don't think there are any JPEG
dll's in my PATH. The path to jpeg/6b.3 in config.inc contains only
libjpeg.lib, which is linked in statically, and best I can tell it
wouldn't even attempt to load a JPEG dll if there were one there.

--
Ron Isaacson
Morgan Stanley
ron.isaacson at morganstanley.com / (212) 276-1144