| That is exactly what I have been saying for a while: _CsoundVST cannot
be both a dylib and a bundle (unlike in other OSs where there is no such
distinction).
Victor
At 14:15 25/05/2006, you wrote:
>There are still some dependencies that result in requiring Python,
>and prevent CsoundVST from working on the Mac. In particular, the
>GUI frontend links against the _CsoundVST library, which requires
>Python because it is a Python module (i.e. it includes a SWIG
>generated wrapper), and it links against _csnd which also requires
>Python. On the Mac only, there are bundle vs. dylib issues when
>linking against any of _csnd or _CsoundVST as long as these are
>also intended to be Python modules.
>So, I think more work may be needed, including the separation of
>the GUI, VST, and Python functionality in such a way that neither
>the GUI nor the VST plugin link against anything that requires
>Python directly or indirectly. Parts of the _CsoundVST library
>that are intended to be usable from Python with 'import CsoundVST'
>may also be moved to _csnd, possibly with the removal of the Boost
>dependency, although that is not very important.
>
>On Thursday 25 May 2006 03:27, Michael Gogins wrote:
>
> > I've updated Csound 5 CVS with changes in CsoundVST so it loads Python
> > dynamically. This should mean that CsoundVST will work as a front and as a
> > VST plugin on computers where Python has not been installed. I would
> > appreciate it if somebody with Mac OS X could test this, if possible,
> before
> > we release the next version.
>--
>Send bugs reports to this list.
>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth |