2008.11.21 21:33 "Re: [Tiff] Patch Legacy App for Updated libtiff?", by Kevin Myers

The entry point WriteScanLine (if exactly spelled like that) does not exist in libtiff, so it stands to reason it was a local modification. If you don't have the source for the locally modified libtiff then I think you are basically hosed.

Well duh, I should have noticed that!!!

After some further poking around the dll files using (gasp) notepad, based on all of the entry point names that I see, it appears that the dll used by my legacy app is *highly* customized. Looks like they might have started with some older version of libtiff, stripped out stuff they didn't think was necessary for their app, and added some of their own gunk. Here are possible entry points that I see which look like they might have come from some version of libtiff:

TIFFAdvanceDirectory
TIFFUnlinkDirectory
TIFFOpen
TIFFReadRawStrip
TIFFFillStrip
TIFFReadRawTile
TIFFFillTile
TIFFReadBufferSetup
TIFFWriteScanline
TIFFWriteEncodedStrip
TIFFWriteRawStrip
TIFFWriteEncodedTile
TIFFWriteRawTile
TIFFWriteBufferSetup
TIFFAppendToStrip

In any case, I suppose that I'm still hosed, right? I don't suppose there is any reasonable way to force calls to these routines in the legacy DLL to go to another dll instead, is there?

:-(