If you don't have .pyd files, you must have a version of Python earlier than 
2.5.

I will refactor the interface libraries. This may take a week or so since I 
am busy with lots of things right now. But I will do it, as I have already 
refactored the VST stuff.

Regards,
Mike

----- Original Message ----- 
From: "Felipe Sateler" 
To: 
Sent: Thursday, August 16, 2007 10:33 PM
Subject: Re: [Cs-dev] Interfaces building


> Michael Gogins wrote:
>
>> For Python: _csnd.pyd contains the actual wrapper code, it links with
>> csnd.so, which contains the Lua wrapper code as well as the C++ interface
>> to Csound, which links with csound64.dll.5.1 which contains the C
>> interface to Csound and the actual Csound implementation.
>
> I don't have any .pyd file. I have csnd.py, which imports _csnd (I guess
> this is _csnd.so). _csnd.so links to lua, python and libcsnd.so (among
> other stuff). libcsnd.so, in turn links to lua, python, and libcsound64.
>
>>
>> There are naming conventions involved. In Python, 'import XXX' means
>> "import XXX.py" and/or dlopen _XXX.pyd.
>>
>> In Lua, 'require("XXX")' or just 'require "XXX"' means read "XXX.lua"
>> and/or dlopen XXX.so.
>>
>> I can just change csnd.so to py_csnd.so, since it is explicitly linked
>> with _csnd.pyd, and that way I keep csnd.so which now will only contain
>> the Lua wrapper code. Both may also explicitly link with a new 
>> cpp_csnd.so
>> which will contain the C++ interface to Csound. This way Python, Java, 
>> and
>> Lua can all use an extension named "csnd."
>
> This sounds cool. So, if I'm getting this right, the reason for linking
> _csnd.so to libcsnd.so is that the c++ interface (which is needed by the
> python bindings) is in there. If that is correct, then I guess the above
> plan would be perfect for my purposes: I could create 4 wrapper packages:
> java, lua, python and c++, with lua and python interfaces depending on the
> c++ bindings.
>
> -- 
>
>  Felipe Sateler
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Would someone be able to explain what is the situation
with the VST opcodes. They cannot be built at the moment
because the headers are gone; are we dropping them from
the releases, or are the headers going to be put back in
somewhere else?

I just wanted to know because I want to fix the scons
build of FLTK widgets on Windows and unless I know what is
going to happen, I can't.

Victor
Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net