2006.04.02 17:30 "Re: [Tiff] WORDS_BIGENDIAN makes libtiff platform dependent (3.8.2) and you have to undefine it on MacTel", by Bob Friesenhahn

On Sat, April 1, 2006 18:57, Bob Friesenhahn said:

The use of WORDS_ENDIAN doesn't really improve performance.

If there is indeed a problem to be fixed (and I am not sure that there is), what solution do you propose to fix it.

Why do we need such define's suddenly now? How was libtiff handling such problems before?

Earlier versions were using a define named 'HOST_BIGENDIAN' in libtiff/tiffconf.h:

• HOST_BIGENDIAN native cpu byte order: 1 if big-endian (Motorola)
• or 0 if little-endian (Intel); this may be used
• in codecs to optimize code

so it does not seem like there was a big change to me. Maybe this had already been figured out before in your build environment and you just did not realize it?

Libtiff really does need to know the endian order, the size of 'short, 'int', 'long', bit order, etc., in order to work correctly for a given target.

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/