On Monday 23 January 2006 19:12, Anthony Kozar wrote:

> Another pre-release issue that occurred to me the other day is whether
> Csound will build correctly on OSes with an "unexpected" endianness.  i.e.
> Will the scons script correctly detect and configure Csound to build on
> Big-endian Linux or BSD (PowerPC, Sparc, Alpha, etc.) and also on
> Intel-processor-based Macs now that they are available??
> 
> I saw a comment in SConstruct the other day that seemed to indicate that it
> always assumes x86 architecture for Linux and PPC for MacOS X.

The comment only relates to the STK opcodes. I do not think there is a
global endianness setting in SConstruct, and, as Csound 5 uses libsndfile,
there are not as many places where this is relevant.
cvanal, hetro, and lpanal always create analysis files with the native
endianness, while the PVOC-EX system detects it at run-time.
The readk/dumpk opcodes also use native endianness. The code that reads
string databases (Top/getstring.c) is written in a way not to depend on
endianness.
One possible place where there may be endianness issues on "unusual"
platforms is the Maldonado soundfont opcodes, but those have always been
very problematic.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net