SWIG can be built (I have done it), boost is header files only but code using boost on OS X needs gcc 4 to compile. I have been trying to build CsoundVST on OSX using a borrowed Mac but interruptions from outside keep happening (work, vacation, etc.). I don't anticipate any particular problems when I get the borrowed Mac upgraded to Tiger which is required to get gcc 4 going.

If you have Tiger it should work to build and install the latest SWIG, then download the latest boost from CVS and then copy the boost header directory into user/local/include, then upgrade to XCode 2.1 with gcc 4, then build CsoundVST.

You can omit to build Loris and other opcodes.

Regards,
Mike

-----Original Message-----
From: David Akbari 
Sent: Aug 25, 2005 11:59 AM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] Csound 5 status

Recently I was looking through ugnorman.c which contains the sources 
for the ATS opcodes but is only implemented as a plugin module for 
Csound4 (at present). I've been trying to convert the API functions 
used in ugnorman.c to use Csound5's API but so far unsuccessful. Things 
like "stderr" and "initerr" are what is most confusing; mostly error 
handling functions in Csound4's API that I'm uncertain of what their 
equivalencies for Csound5 are (although I think the initerror one is 
csound->Die() ??)

It would seem that these opcodes (ATS) would be a worthwhile addition 
to Csound5's already extensive library of spectral / streaming / etc 
opcodes and could provide even more reasons to use Csound as opposed to 
another software synthesizer (eg SuperCollider). Other than that, it 
would seem that the API is much cleaner / easily accessible as it is 
implemented today than even just one month ago.

Performance on Mac OSX is adequate, albeit slower than Csound5 on x86 
processors - as the average Mac processor can be as little as 1/3 as 
fast as a typical x86 processor. Mostly everyone I've talked to that 
desires to use Csound5 on the Mac is talking about the need for an 
easily accessible frontend (like MacCsound) but with Csound5's crucial 
updates (of course there is also Blue for this purpose) -- the typical 
professional studio musician that would use Csound on the Mac is also a 
person who loathes using the commandline and prefers to stick to pretty 
GUI's like Logic, for example. Personally I've found Victor's 
csoundapi~ for Pd to be a wonderful compromise.

Since I've began using Csound5 on OSX, I have still yet to be able to 
compile CsoundVST (can SWIG and Boost be built on OSX?) due to library 
dependencies that reach beyond the scope of the canonical sources as 
well as extension modules (like Loris and the python opcodes) which 
rely on CsoundVST (or the Boost/SWIG headers). I have all the required 
external sources in the correct places, and the SConstruct flags 
reflect the intent to compile these modules accordingly, however still 
no go. Has anyone been successful yet in this pursuit? I'm dying to 
hear about someone doing this - it would certainly be a welcome 
inspiration.

Anyway, Istvan periodically mentions "to be at or better than the 
status of Csound4" to be a requisite for the release of Csound5 and I 
personally feel like the present status of Csound5 has more than 
surpassed this (on Windows, Linux, and Mac OSX at least - I don't have 
access to a computer that runs Irix or Solaris).

All things considered, it almost feels like Csound5 was released a 
month or more ago. The only reason I use anything related to Csound4 
anymore is solely for MacCsound.

$0.02 well spent,
-David

On Aug 25, 2005, at 8:36 AM, Istvan Varga wrote:

> One month after the previous review of what is left to do before
> releasing Csound 5, it is time to update the information on
> development status. Does anyone have suggestions on major issues
> to be solved, or any (even if small) incompatible changes to the
> API that should be done ? What is required to have a "release
> candidate" version ?
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>

-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk



-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk