****** Forwarded Message Follows *******

But you have to do it yourself, as I don't know anything
about
the CsoundVST code or where to edit it. I am just trying to
build it.
I am not building a dylib, by the way, but a bundle
called _CsoundVST.so (for lack of a better extension).

The Sconstruct as it was was linking CsoundVST
to _CsoundVST. I did not do it, so it's probably wrong
for linux and windows as well, if you are not supposed
to link. The code was outside any if statements as far
as I could see.

So how do you this on Linux then?

Victor
>
> This is where you have to (1) load the _CsoundVST.dylib
> explicitly, then (2) get the CreateCsoundVST function
> explicitly, as I do it on Windows. You will NOT link to
> any _CsoundVST library. Instead, _CsoundVST.dylib will
> become a plugin for the CsoundVST application.
>
> The latest 2.4 SDK for VST from Steinberg is supposed to
> make it work better on OS X. That's all I can say since
> I've haven't experienced the issues for myself...
>
> Thanks,
> Mike
>
> -----Original Message-----
> >From: Victor Lazzarini 
> >Sent: May 25, 2006 4:03 PM
> >To: Michael Gogins 
> >Subject: Re: [Csnd] CsoundVST with dynamic loading of
> Python >
> >Anyway, I tried building csoundVST and here's what I have
> to >report:
> >
> >- if as you say _CsoundVST is not be linked against, then
> >the
> >following line (1529) in sconstruct has to be commented
> out: >
> >guiProgramEnvironment.Prepend(LIBS = ['_CsoundVST'])
> >
> >and and if... has to be added to the ShareLibrary builder
> >
> > if getPlatform() != 'darwin':
> >      csoundvst =
> >vstEnvironment.SharedLibrary('_CsoundVST',
> csoundVstSources) >
> >This is fine. But then when linking CsoundVST I get:
> >
> >g++ -o CsoundVST frontends/CsoundVST/csoundvst_main.o -L.
> >-L. -L/usr/local/
> >lib -L. -L. -lstdc++ -lpthread -lm
> >ld: Undefined symbols:
> >_CreateCsoundVST
> >
> >
> >I've updated SConstruct with the above changes, but
> there's >more to be done.
> >
> >Victor
> >
> >>
> >> This will require an #ifdef in the CsoundVST
> application >> (not the _CsoundVST library) that will load
> _CsoundVST as >> a dylib on OS X, similarly to the way it
> is currently on >> for WIN32.
> >>
> >> Regards,
> >> Mike
> >>
> >> -----Original Message-----
> >> >From: Victor Lazzarini 
> >> >Sent: May 25, 2006 2:38 PM
> >> >To: Michael Gogins 
> >> >Subject: Re: [Csnd] CsoundVST with dynamic loading of
> >> Python >
> >> >That's a bundle then, we have to build _CsoundVST as a
> >> >bundle. The
> >> >difference between a bundle and a dylib is exactly
> that: >> you >link
> >> >against a dylib and you load a bundle. I will try it
> and >> >come
> >> >back to you.
> >> >
> >> >Victor
> >> >
> >> >>
> >> >> Of course, that's only on Windows. Can the same
> thing >> be >> done on OS X?
> >> >>
> >> >> -----Original Message-----
> >> >> >From: Michael Gogins 
> >> >> >Sent: May 25, 2006 1:10 PM
> >> >> >To: csound@lists.bath.ac.uk
> >> >> >Subject: Re: [Csnd] CsoundVST with dynamic loading
> of >> >> Python >
> >> >> >Also, just to make this perfectly clear, CsoundVST
> >> does >> NOT link with the _CsoundVST shared library.
> >> Instead, >> CsoundVST dynamically loads the _CsoundVST
> >> shared library >> at run time. >
> >> >> >What is the difference between a bundle and a dylib
> , >> >> anyway? >
> >> >> >Regards,
> >> >> >Mike
> >> >> >
> >> >> >-----Original Message-----
> >> >> >>From: Victor Lazzarini 
> >> >> >>Sent: May 25, 2006 12:21 PM
> >> >> >>To: csound@lists.bath.ac.uk
> >> >> >>Subject: Re: [Csnd] CsoundVST with dynamic loading
> of >> >> Python >>
> >> >> >>No, it's a link problem: you cannot 'import
> >> CsoundVST' >> from python because >>_CsoundVST.so is a
> >> dylib, but if you >> make it a bundle, then you cannot
> >> link  >>CsoundVST >> >>to it. It can't be both things.
> But >> if you use csnd.py >> (_cnsd.so) as your  >>python
> module, >> >> >>then it might be possible to make things
> work >> (perhaps >> in a similar way to  >>how you do
> >> >> >>it in the fltk Csound5GUI).
> >> >> >>
> >> >> >>Victor
> >> >> >>
> >> >> >>At 17:00 25/05/2006, you wrote:
> >> >> >>>I thought that the problem was a runtime problem,
> >> not a >> link time problem.  >>>In other words, I
> thought >> it would >> be possible to LINK CsoundVST and
> >> >>>_CsoundVST.so on OS >> X (linking with Python of
> >> course), but then RUN >> >>>CsoundVST WITHOUT Python.
> >>> >> >> >>>CsoundVST creates 2 instances of the
> CsoundVST class >> -- >> one as a C++  >>>object and one
> as a Python object. >> When >> using Python, obviously the
> Python  >>>object is >> used, but >> it is also plugged
> into the GUI and replaces >> the C++ >> >>>instance. >>>
> >> >> >>>I assume that CsoundVST will run on Windows if
> >> Python >> is not in the  >>>environment -- I will
> confirm >> that. >> >>>
> >> >> >>>Can you LINK CsoundVST?
> >> >> >>>
> >> >> >>>Regards,
> >> >> >>>Mike
> >> >> >>>
> >> >> >>>-----Original Message-----
> >> >> >>> >From: Istvan Varga 
> >> >> >>> >Sent: May 25, 2006 9:15 AM
> >> >> >>> >To: csound@lists.bath.ac.uk
> >> >> >>> >Subject: Re: [Csnd] CsoundVST with dynamic
> loading >> of >> Python >>> >
> >> >> >>> >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 >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>--
> >> >> >>>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
> >> >> >>
> >> >> >>--
> >> >> >>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
> >>
> >>
> >>
>
>
>