[Csnd] removing csound(s)
| Date | 2013-06-20 05:39 |
| From | DavidWorrall |
| Subject | [Csnd] removing csound(s) |
How does one remove all traces of non-bespokely-installed csounds from the three main HW platforms? "remove csound" in the csounds.com search engine returned
to which no one has (yet) responded Does one have to remove any csound libraries/ object files from the python Framework(s)? thanks, David _____________________________________________ Dr David Worrall Experimental Composer, Polymedia Adjunct Senior Research Fellow, Australian National University Board Member, International Community for Auditory Display Regional Editor, Organised Sound (CUP) |
| Date | 2013-06-20 13:14 |
| From | Michael Gogins |
| Subject | Re: [Csnd] removing csound(s) |
On Ubuntu 12.04 LTS I run Csound 6 with Python 2.7.3. On Windows 8 I run Csound 6 with Python 2.7.3. The Python versions I use have not changed from Csound 5.19.
Please note, because the Python interface to Csound is generated by SWIG, the user's version of Python must match the version of Python used by SWIG. To build the WIndows installers, I used Python 2.7.3.
If you download Python 2.7.3 from http://www.python.org/download/releases/ and install everything with defaults, and the WIndows installers for either Csound 5.19 or Csound 6 from SourceForge, it should work fine for WIndows. Probably Python 2.7.5, the most recent version of 2.7, would also work.
I have not tried to install Csound from packages on Linux because I build it from sources. If you install Python 2.7 on Linux and build Csound from sources it should work, as it does for me, but you may have to set the Python paths and versions in the build system.
Hope this helps, Mike =========================== Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Thu, Jun 20, 2013 at 12:39 AM, DavidWorrall <vip@avatar.com.au> wrote:
|
| Date | 2013-06-21 05:16 |
| From | DavidWorrall |
| Subject | Re: [Csnd] removing csound(s) |
| Thanks, Michael. I'm trying to read between the lines here: but, to your knowledge, Do you think this is correct?: On a system with multiple version of Python, does SWIG generate the Python wrappers (for csound etc) using the user's "current" python? Or is there a dependency the other way as well, ie. does one need to build SWIG (from source) with the same Python target in place as will be used for the csound wrappers? (should this discussion be on the dev list? if so I'll swap it over) David On 20/06/2013, at 10:14 PM, Michael Gogins wrote:
________________________________________________ Dr David Worrall. - Experimental Polymedia: worrall.avatar.com.au - Sonification: www.sonification.com.au - Education for Financial Independence: www.mindthemarkets.com.au |
| Date | 2013-06-21 08:25 |
| From | Victor Lazzarini |
| Subject | Re: [Csnd] removing csound(s) |
I think the main thing here is not SWIG, but linking. If you link to a given library from a given installation, then you have to use that one. On OSX, for instance, that is what happens. So in order to use Anaconda or etc, you need to link to their libs. It might be the case of just changing the lib dependency on the actual module (with install_name_tool), or in the case of Windows just to use a different DLL (instead of the one originally linked to). Or it might need to be re-linked. Victor On 21 Jun 2013, at 05:16, DavidWorrall wrote:
Dr Victor Lazzarini Senior Lecturer Dept. of Music NUI Maynooth Ireland tel.: +353 1 708 3545 Victor dot Lazzarini AT nuim dot ie |
| Date | 2013-06-21 11:00 |
| From | Michael Gogins |
| Subject | Re: [Csnd] removing csound(s) |
Swig generates wrappers based on the python header files. These will be the ones for the instance of python that executes in swig's environment. On Jun 21, 2013 12:16 AM, "DavidWorrall" <vip@avatar.com.au> wrote:
|