Hi Dave,

Rather than copy files into the python/lib/site-packages or anything
like that, I think you can just define PYTHONPATH and add the location
of where csnd.py, _csnd.so, etc. are.  i.e. if I compile csound in
/home/steven/workspace/csound5, you can just set PYTHONPATH to that
directory.  (At least, that's what I did on Windows and that worked).

Could you try that?

steven

On Thu, May 8, 2008 at 1:24 PM, Dave Phillips <dlphillips@woh.rr.com> wrote:
> Victor Lazzarini wrote:
>
> > There should be a libcsnd.so.5.1 because if you build it from
> > sources, then _csnd.so is linked to it and if it doesn't exist,
> > the build would have failed.
> >
>  Sorry, yes it is there. However, it is not linked to _csnd.so, they are
> separate files.
>
>  I tried Bruce's script, got a no-go after that too. I try this:
>
>  python main.py
>
>  And I get this:
>
>
>  dlphilp@64studio:~/barebones$ python main.py
>  Traceback (most recent call last):
>   File "main.py", line 13, in <module>
>    import csnd
>   File "/usr/local/lib/python2.5/site-packages/csnd.py", line 7, in <module>
>    import _csnd
>  ImportError: libcsnd.so.5.1: cannot open shared object file: No such file
> or directory
>
>
>  Libcsnd.so is in the plugins directory, AFAICT it's a stripped copy of
> libcsnd.so.5.1. There is a file named _csnd.so sitting in the top level of
> my Csound source build. Is it supposed to be somewhere else ?
>
>  Sorry, I'm still not clear about what exactly is supposed to go from Csound
> into the Python site-packages folder in order to run Oeyvind's code.
>
>
>
>  Best,
>
>  dp
>
>
>
>  Send bugs reports to this list.
>  To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>