2006.04.01 04:44 "[Tiff] WORDS_BIGENDIAN makes libtiff platform dependent
(3.8.2) and you have to undefine it on MacTel", by ping shu
Thread
2006.04.01 18:56 "Re: [Tiff] WORDS_BIGENDIAN makes libtiff platform dependent (3.8.2) and you have to undefine it on MacTel", by ping shu
--- Bob Friesenhahn <bfriesen@simple.dallas.tx.us> wrote:
Version 3.8.2 requires WORDS_BIGENDIAN Defined or UNdefined correctly now. I think it is a bad thing. I had code that worked on Win, Mac/PPC, MacTel, now the Mac/PPC is broken unless I define WORD_BIGENDIAN to 1 and UNdefine it on Mactel.
Can we get rid of such dependecy?
There are code that uses libtiff but doesn't use the "config" utility.
Libtiff itself has this dependency, but not the public headers which should be used by dependent applications. What header are you including which brings in the WORD_BIGENDIAN requirement?
I am pretty sure that pre-configure libtiff also depended on an endian define, but the name was different.
Yes, an app shoudl be fine if it uses the public header files and system installed libtiff. If an app builds the libtiff (e.g. porting to a Portable Media Player), then
the developers may think twice upgrading to 3.8.2.
A related issue I found is the use of
#ifdef WORDS_BIGENDIAN
...1
#else
...2
#endif
Section 1 is used if you do
#define WORDS_BIGENDIAN 0
and hope for section 2. The other def HOST_ENDIAN is
not
in use and it is either 0 or 1.
The use of WORDS_ENDIAN doesn't really improve performance.
Ping
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com