On Tue, Apr 10, 2001 at 08:02:38PM +0200, Michel Dänzer wrote:
>David Dawes wrote:
>
>> Log message:
>> Use X_BYTE_ORDER rather than the non-portable endian.h
>>
>> Modified files:
>> xc/xc/lib/GL/mesa/src/drv/r128/:
>> Imakefile.inc r128_context.h r128_tex.h r128_tris.c
>> r128_vb.h
>
>I used that in my first attempts on the ppc branch but Gareth told me not to
>because the code might get used outside of X at some point.
>
>What's the current situation?
If it's used outside of X, then you can duplicate the way we're doing
it in X, or come up with a different abstraction that is portable.
Using <endian.h> and it's associated macros directly breaks building
this code on FreeBSD (currently the only non-Linux platform for which
building the DRI modules is enabled).
FWIW, we went through a lot of iterations on how to handle this within
the XFree86 source tree, and the method we ended up using was the only
one we tried that worked reliably and portably. Take a look at
xc/include/Xarch.h too see how many different ways this is handled on
different platforms.
David
--
David Dawes Email: [EMAIL PROTECTED]
Founder/President, The XFree86 Project, Inc Phone: +1 510 687 6857
http://www.xfree86.org/
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
