2005.08.22 18:54 "RE: [Tiff] win32 libtiff", by Mark R. Olin
Yeah, I am getting the drift of what Larry, Jeff and Edward are saying. I am trying different things along those lines, including adding the /MDd to "makefile.vc" and to the command line link options in Codewarrior.
And I don't set the flag for JPEG_SUPPORT, so it only creates binaries for libtiff.dll and libtiff.lib, and my program only requires the libtiff.dll now.
But still no luck. Same error:
"Invalid Address specified to RtlFreeHeap"
I will check out the light reading at the msdn weblink that Jeff gave me and try to get better insight into this peculiar problem.
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org] On Behalf Of Larry Grill
> Sent: Friday, August 19, 2005 6:59 PM
> To: email@example.com
> Subject: Re: [Tiff] win32 libtiff
Yeah, like Jeff said.
I've run into similar strangeness. If you are linking zlib and jpeg you should also compile those with the same static or multithreaded options or you can run into problems.
Check to make sure your program and libtiff were compiled
> against the
same runtime, i.e. all the /MDd or /MT or /ML or whatever
compiler flags are the same across all the software. I've found
> things can
almost - but not quite - work when there is
On Fri, 2005-08-19 at 13:37 -0700, Mark R. Olin wrote:
I was able to compile a binary lib and dll using "nmake" (begrudgingly), which is a MS Visual Studio utility (I have it, but don't use much).
I read comments in "makefile.vc" in the libtiff distribution which said to execute
nmake /f makefile.vc all
and that worked to supply me with natively compiled libtiff.lib and libtiff.dll.
Linking them into my program using Codewarrior IDE, I am
> able to use
the TIFF routines successfully again, but with the same
> unusual Access
Violation and runtime error in ntdll.dll.
Invalid Address specified to RtlFreeHeap( 00140000, 0014A2F8 )
Since I am using two different linking environments,
> Codewarrior and
MSVC, I am thinking that the problem lies there.
Anyway, thanks to Edward L. for the new direction.
I'll work with Cygwin gcc and make and let you know how it goes. Gotta install Cygwin first though.
I really recommend setting up make. There's a win32 version of make that you can compile as well although I'm not sure how well it works. We're using the cygwin version of gnu make.
> http://lists.maptools.org/mailman/listinfo/tif> f