trekiej wrote:
I wonder if those who have an OS that is big and little endian per cpu have a developement tool chain capable of handling both?
How did BeOS cope?
No idea about BeOS, but it's common to have a header file such as
endian.h that indicates which type the current CPU uses. Most software developers don't have to worry about endianness, but when you start doing things that access hardware directly, or read/write stuff to/from disk or streams, CPU endianness does make a difference. For example, a CD/DVD-writer app for AROS would have to take CPU endianness into account as it accesses the CD/DVD drive at a low level. Otherwise, it would work either on AROS x86, or on PowerPC, but not both.
Hans