[Cs-dev] how to get involved in development
Date | 2009-06-30 21:13 |
From | Brian Redfern |
Subject | [Cs-dev] how to get involved in development |
Hi guys, beyond giving advice to other csound users, I'm wondering how I could best get involved in the actual development of csound? I've been able to build from source on mac osx and linux, and I also have a windows dev box. One project I was thinking about was to bring the csound api to Ruby so that Ruby users can have the same api available as the Python users, like bringing CsoundAC to Ruby. But I also know C and could help out on a lower level as well. ------------------------------------------------------------------------------ _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2009-07-02 13:12 |
From | joachim heintz |
Subject | Re: [Cs-dev] how to get involved in development |
Hi Brian - sorry for just picking a minor point from your mail. You said that you are building Csound from source on osx. Is there a good description for doing that? Thanks - joachim Am 30.06.2009 um 22:13 schrieb Brian Redfern: > Hi guys, beyond giving advice to other csound users, I'm wondering how > I could best get involved in the actual development of csound? I've > been able to build from source on mac osx and linux, and I also have a > windows dev box. > > One project I was thinking about was to bring the csound api to Ruby > so that Ruby users can have the same api available as the Python > users, like bringing CsoundAC to Ruby. > > But I also know C and could help out on a lower level as well. > > ------------------------------------------------------------------------------ > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------------ _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2009-07-02 16:55 |
From | Jacob Joaquin |
Subject | Re: [Cs-dev] how to get involved in development |
I would also like to get involved, and curious of the process. I'm already working on some things behind the scenes. It's just a matter of time before I'm ready to officially dive into official Csound development. Best, Jake Brian Redfern-2 wrote: > > Hi guys, beyond giving advice to other csound users, I'm wondering how > I could best get involved in the actual development of csound? I've > been able to build from source on mac osx and linux, and I also have a > windows dev box. > > One project I was thinking about was to bring the csound api to Ruby > so that Ruby users can have the same api available as the Python > users, like bringing CsoundAC to Ruby. > > But I also know C and could help out on a lower level as well. > > ------------------------------------------------------------------------------ > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > > -- View this message in context: http://www.nabble.com/how-to-get-involved-in-development-tp24278829p24309328.html Sent from the Csound - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2009-07-02 17:47 |
From | Jeremy Voorhis |
Subject | Re: [Cs-dev] how to get involved in development |
Attachments | None None |
I've been able to build Csound5 from source on OS X 10.5 by following the instructions at http://www.csounds.com/manual/html/BuildingCsound.html. I used quite a few of the non-standard flags to build against CoreMIDI and CoreAudio instead of PortMIDI and PortAudio, which I always seem to have trouble with on OS X. Also, I had to patch the latest stable release of Csound5 to build it on my case-sensitive filesystem, but that seems to be fixed in CVS HEAD. When I get back to my laptop later tonight, I can post my build script to the list. Best, Jeremy
On Thu, Jul 2, 2009 at 5:12 AM, joachim heintz <jh@joachimheintz.de> wrote: Hi Brian - |
Date | 2009-07-03 09:54 |
From | Victor.Lazzarini@nuim.ie |
Subject | Re: [Cs-dev] how to get involved in development |
Attachments | None None None |