AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
October 2007

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2007.10.23 08:38 "universal build patch", by Kai-uwe Behrmann
2007.10.23 15:37 "Re: universal build patch", by Bob Friesenhahn
2007.10.23 15:50 "Re: universal build patch", by Andrey Kiselev
2007.10.23 16:12 "Re: universal build patch", by Bob Friesenhahn
2007.10.23 19:17 "Re: universal build patch", by Andrey Kiselev
2007.10.23 20:44 "Re: universal build patch", by Bob Friesenhahn
2007.10.24 07:19 "Re: universal build patch", by Andrey Kiselev
2007.10.24 08:32 "Re: universal build patch", by Kai-uwe Behrmann
2007.10.24 11:26 "Re: universal build patch", by Andrey Kiselev
2007.10.24 15:44 "Re: universal build patch", by Bob Friesenhahn
2007.10.23 20:56 "Re: universal build patch", by Toby Thain

2007.10.23 19:17 "Re: universal build patch", by Andrey Kiselev

On Tue, Oct 23, 2007 at 11:12:33AM -0500, Bob Friesenhahn wrote:
> >We can easily switch to this method instead of autoconf macro. I am
> >only concerning about portability of this approach.
> 
> It is 100% portable as long as you stick to using Apple's modified GCC
> 4.X and OS X.  Other targets are of no consequence.  :-)
> 
> Solaris defines _LITTLE_ENDIAN or _BIG_ENDIAN by including 
> <sys/types.h>
...
> My feeling is that it the only completely correct approach is to
> configure/build on each native target since otherwise some decisions
> made may be wrong.  Perhaps 32-bit OS X has managed to constrain PPC
> and Intel differences to only endian order but this is the exception
> rather than the rule.  With Mac OS X Leopard (Arriving October 26)
> perhaps the rules will change (the rules for Apple always change).

I am sure that AC_C_BIGENDIAN macro can deduce the target byte order
using some heuristics (that macro works in case of cross-compilation).
So it can be adopted for OS X case too. The only problem for me is that
I do not have a proper environment to develop and test such a macro. It
shouldn't be too complicated. So my preference is to modify a test
rather than libarary itself. I don't see any serious reason to replace
the compile time switch.

Best regards,
Andrey


-- 
Andrey V. Kiselev
ICQ# 26871517