AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2007.06.29 11:04 "[Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.29 12:49 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Frank Warmerdam
2007.06.29 18:18 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.29 13:12 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Andrey Kiselev
2007.06.29 19:58 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.30 07:29 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.29 15:17 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Bob Friesenhahn

2007.06.30 07:29 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers

Hello Andrey,

Please see below.

Thanks,

Kevin M.

In a prior message, "Kevin Myers" wrote in part:

<snip>

However, while looking back at all of the above I noticed another change that I had to make in jmorecfg.h that *did* result in compiler errors while building libtiff if left unchanged. The jmorecfg.h that I was using contains the following block of code:

#if (defined (_MSC_VER) && (_MSC_VER >= 800))
#define HAVE_UNSIGNED_CHAR
#define HAVE_ALL_INTS
#define EXTERN(type) extern type __cdecl
#endif

I had to comment out the #define HAVE_ALL_INTS, otherwise a block of code that includes typedefs for UINT8 and UINT16 (among other things) is bypassed, and this causes problems when the libtiff build tries to process jpeglib.h, which contains items that are defined as types UINT8 and UINT16.

It looks like the above problem also turns out to be due to an error on my part. I had a few environment variables pointing to the wrong directories for my build environment. After I corrected that problem, the original version of jmorecfg worked properly without any modifications.

Sorry for the false alarm.