Here is another question that I hope someone will be able to answer.

If I generate the python wrapper code on another platform (say MacOS X), do
you think that it will compile and work properly on MacOS 9?

I had the Python interface working before it was changed to use C++.  Now
the only version of Swig available on MacOS 9 fails processing the .i file.

Thanks.

Anthony Kozar
anthonykozar AT sbcglobal DOT net



-------------------------------------------------------
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

Thanks, Istvan!

I will give it a try.  Word size and endianness are of course the same.  The
only problem might be the __THREAD__ macro.  Thanks for the heads-up on that
one.

Anthony

Istvan Varga wrote on 2/4/06 5:05 AM:

> The wrapper files generated by SWIG do not seem to be platform dependent,
> other than some optional thread locking stuff in python_interface_wrap.h
> that is enabled only if the macro __THREAD__ is defined. At least I can
> create the wrapper sources on Linux and then compile for Win32 and the
> resulting modules seem to work.
> It is probably worth giving a try, especially if MacOS 9 and X have the
> same word size and endianness.



-------------------------------------------------------
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