Csound Csound-dev Csound-tekno Search About

[Cs-dev] manual update needed on adding own opcode?

Date2012-01-05 04:16
FromIain Duncan
Subject[Cs-dev] manual update needed on adding own opcode?
AttachmentsNone  None  
Hi folks, I'd be happy to update it if no one else wants to, though not sure what the deal is these days with access to sources.

It looks like this page:

has a confusing or out of date section here:

(begin quote)
Add your plugin as a new target in the plugin opcodes section of the SConstruct build file:

pluginEnvironment.SharedLibrary('newgen',
Split('''Opcodes/newgen.c
Opcodes/another_file_used_by_newgen.c
Opcodes/yet_another_file_used_by_newgen.c'''))

(end quote)

When I look in Sconstruct, I don't see any other instances of "pluginEnvironment.SharedLibrary", and all I seemed to have to do to add my opcode was add:

makePlugin(pluginEnvironment, 'myop', ['Opcodes/myop.c'])

Go coconut walky-talkies! cargo cult programming in action.... if someone can verify that this is indeed the proper way to land the planes with my coconuts, I'd be happy to update the manual. But I really have no idea what I'm doing there, beyond imitating what seems to be already there.

Thanks!
Iain



Date2012-01-05 09:36
FromVictor Lazzarini
SubjectRe: [Cs-dev] manual update needed on adding own opcode?
AttachmentsNone  None  
My impression is that both will work. makePlugin() calls SharedLibrary.

Victor
On 5 Jan 2012, at 04:16, Iain Duncan wrote:

Hi folks, I'd be happy to update it if no one else wants to, though not sure what the deal is these days with access to sources.

It looks like this page:

has a confusing or out of date section here:

(begin quote)
Add your plugin as a new target in the plugin opcodes section of the SConstruct build file:

pluginEnvironment.SharedLibrary('newgen',
Split('''Opcodes/newgen.c
Opcodes/another_file_used_by_newgen.c
Opcodes/yet_another_file_used_by_newgen.c'''))

(end quote)

When I look in Sconstruct, I don't see any other instances of "pluginEnvironment.SharedLibrary", and all I seemed to have to do to add my opcode was add:

makePlugin(pluginEnvironment, 'myop', ['Opcodes/myop.c'])

Go coconut walky-talkies! cargo cult programming in action.... if someone can verify that this is indeed the proper way to land the planes with my coconuts, I'd be happy to update the manual. But I really have no idea what I'm doing there, beyond imitating what seems to be already there.

Thanks!
Iain


------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




Date2012-01-05 09:50
FromRory Walsh
SubjectRe: [Cs-dev] manual update needed on adding own opcode?
Hi Iain. You probably know this already but if you create a plugin
opcode you don't need to use scons at all, which in turn means you
don't have to keep rebuilding Csound. Victor put together a paper on
building plugin opcodes:

http://www.csounds.com/articles/Extensions_to_Csound.pdf

I find it much handier to build opcodes this way.

Rory.



On 5 January 2012 05:16, Iain Duncan  wrote:
> Hi folks, I'd be happy to update it if no one else wants to, though not sure
> what the deal is these days with access to sources.
>
> It looks like this page:
> http://www.csounds.com/manual/html/csound5extending.html
>
> has a confusing or out of date section here:
>
> (begin quote)
> Add your plugin as a new target in the plugin opcodes section of the
> SConstruct build file:
>
> pluginEnvironment.SharedLibrary('newgen',
> Split('''Opcodes/newgen.c
> Opcodes/another_file_used_by_newgen.c
> Opcodes/yet_another_file_used_by_newgen.c'''))
>
> (end quote)
>
> When I look in Sconstruct, I don't see any other instances of
> "pluginEnvironment.SharedLibrary", and all I seemed to have to do to add my
> opcode was add:
>
> makePlugin(pluginEnvironment, 'myop', ['Opcodes/myop.c'])
>
> Go coconut walky-talkies! cargo cult programming in action.... if someone
> can verify that this is indeed the proper way to land the planes with my
> coconuts, I'd be happy to update the manual. But I really have no idea what
> I'm doing there, beyond imitating what seems to be already there.
>
> Thanks!
> Iain
>
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2012-01-05 17:16
FromIain Duncan
SubjectRe: [Cs-dev] manual update needed on adding own opcode?
AttachmentsNone  None  
Thanks guys. Don't you think both of these answers should be included in the manual page I referenced? I don't mind updating it if I have access to that and someone tells me the procedure. And double checks my changes I guess.  

iain

On Thu, Jan 5, 2012 at 1:36 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
My impression is that both will work. makePlugin() calls SharedLibrary.

Victor
On 5 Jan 2012, at 04:16, Iain Duncan wrote:

Hi folks, I'd be happy to update it if no one else wants to, though not sure what the deal is these days with access to sources.

It looks like this page:

has a confusing or out of date section here:

(begin quote)
Add your plugin as a new target in the plugin opcodes section of the SConstruct build file:

pluginEnvironment.SharedLibrary('newgen',
Split('''Opcodes/newgen.c
Opcodes/another_file_used_by_newgen.c
Opcodes/yet_another_file_used_by_newgen.c'''))

(end quote)

When I look in Sconstruct, I don't see any other instances of "pluginEnvironment.SharedLibrary", and all I seemed to have to do to add my opcode was add:

makePlugin(pluginEnvironment, 'myop', ['Opcodes/myop.c'])

Go coconut walky-talkies! cargo cult programming in action.... if someone can verify that this is indeed the proper way to land the planes with my coconuts, I'd be happy to update the manual. But I really have no idea what I'm doing there, beyond imitating what seems to be already there.

Thanks!
Iain


------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel



Date2012-01-07 17:42
FromIain Duncan
SubjectRe: [Cs-dev] manual update needed on adding own opcode?
AttachmentsNone  None  
Ping? Really. the manual should be updated to reflect whatever is now common practice. Out of date docs are a Bad Thing. I'm volunteering to make this update if anyone wants to talk to me about what I need to do in order to do so.

thanks
Iain

On Thu, Jan 5, 2012 at 9:16 AM, Iain Duncan <iainduncanlists@gmail.com> wrote:
Thanks guys. Don't you think both of these answers should be included in the manual page I referenced? I don't mind updating it if I have access to that and someone tells me the procedure. And double checks my changes I guess.  

iain

On Thu, Jan 5, 2012 at 1:36 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
My impression is that both will work. makePlugin() calls SharedLibrary.

Victor
On 5 Jan 2012, at 04:16, Iain Duncan wrote:

Hi folks, I'd be happy to update it if no one else wants to, though not sure what the deal is these days with access to sources.

It looks like this page:

has a confusing or out of date section here:

(begin quote)
Add your plugin as a new target in the plugin opcodes section of the SConstruct build file:

pluginEnvironment.SharedLibrary('newgen',
Split('''Opcodes/newgen.c
Opcodes/another_file_used_by_newgen.c
Opcodes/yet_another_file_used_by_newgen.c'''))

(end quote)

When I look in Sconstruct, I don't see any other instances of "pluginEnvironment.SharedLibrary", and all I seemed to have to do to add my opcode was add:

makePlugin(pluginEnvironment, 'myop', ['Opcodes/myop.c'])

Go coconut walky-talkies! cargo cult programming in action.... if someone can verify that this is indeed the proper way to land the planes with my coconuts, I'd be happy to update the manual. But I really have no idea what I'm doing there, beyond imitating what seems to be already there.

Thanks!
Iain


------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




Date2012-01-08 08:00
FromAndres Cabrera
SubjectRe: [Cs-dev] manual update needed on adding own opcode?
Hi Iain,

The manual is kept in git, and is written in docbook-xml. You just
need to edit these files, just being careful about the xml tags, to
make sure you close them properly and to not introduce tags that are
invalid in docbook-xml. If you ask John for permission, he will give
you write access so you can commit your changes.

There is a readme file in the manual root directory where you will
find instructions on how to build the manual.

Cheers,
Andrés

On Sat, Jan 7, 2012 at 5:42 PM, Iain Duncan  wrote:
> Ping? Really. the manual should be updated to reflect whatever is now common
> practice. Out of date docs are a Bad Thing. I'm volunteering to make this
> update if anyone wants to talk to me about what I need to do in order to do
> so.
>
> thanks
> Iain
>
> On Thu, Jan 5, 2012 at 9:16 AM, Iain Duncan 
> wrote:
>>
>> Thanks guys. Don't you think both of these answers should be included in
>> the manual page I referenced? I don't mind updating it if I have access to
>> that and someone tells me the procedure. And double checks my changes I
>> guess.
>>
>> iain
>>
>> On Thu, Jan 5, 2012 at 1:36 AM, Victor Lazzarini
>>  wrote:
>>>
>>> My impression is that both will work. makePlugin() calls SharedLibrary.
>>>
>>> Victor
>>> On 5 Jan 2012, at 04:16, Iain Duncan wrote:
>>>
>>> Hi folks, I'd be happy to update it if no one else wants to, though not
>>> sure what the deal is these days with access to sources.
>>>
>>> It looks like this page:
>>> http://www.csounds.com/manual/html/csound5extending.html
>>>
>>> has a confusing or out of date section here:
>>>
>>> (begin quote)
>>> Add your plugin as a new target in the plugin opcodes section of the
>>> SConstruct build file:
>>>
>>> pluginEnvironment.SharedLibrary('newgen',
>>> Split('''Opcodes/newgen.c
>>> Opcodes/another_file_used_by_newgen.c
>>> Opcodes/yet_another_file_used_by_newgen.c'''))
>>>
>>> (end quote)
>>>
>>> When I look in Sconstruct, I don't see any other instances of
>>> "pluginEnvironment.SharedLibrary", and all I seemed to have to do to add my
>>> opcode was add:
>>>
>>> makePlugin(pluginEnvironment, 'myop', ['Opcodes/myop.c'])
>>>
>>> Go coconut walky-talkies! cargo cult programming in action.... if someone
>>> can verify that this is indeed the proper way to land the planes with my
>>> coconuts, I'd be happy to update the manual. But I really have no idea what
>>> I'm doing there, beyond imitating what seems to be already there.
>>>
>>> Thanks!
>>> Iain
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>>> infrastructure or vast IT resources to deliver seamless, secure access to
>>> virtual desktops. With this all-in-one solution, easily deploy virtual
>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>>> costs. Try it free!
>>> http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> Dr Victor Lazzarini
>>> Senior Lecturer
>>> Dept. of Music
>>> NUI Maynooth Ireland
>>> tel.: +353 1 708 3545
>>> Victor dot Lazzarini AT nuim dot ie
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>>> infrastructure or vast IT resources to deliver seamless, secure access to
>>> virtual desktops. With this all-in-one solution, easily deploy virtual
>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https

Date2012-01-09 18:17
FromIain Duncan
SubjectRe: [Cs-dev] manual update needed on adding own opcode?
AttachmentsNone  None  
Thanks Andres. 

Iain

On Sun, Jan 8, 2012 at 12:00 AM, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Iain,

The manual is kept in git, and is written in docbook-xml. You just
need to edit these files, just being careful about the xml tags, to
make sure you close them properly and to not introduce tags that are
invalid in docbook-xml. If you ask John for permission, he will give
you write access so you can commit your changes.

There is a readme file in the manual root directory where you will
find instructions on how to build the manual.

Cheers,
Andrés

On Sat, Jan 7, 2012 at 5:42 PM, Iain Duncan <iainduncanlists@gmail.com> wrote:
> Ping? Really. the manual should be updated to reflect whatever is now common
> practice. Out of date docs are a Bad Thing. I'm volunteering to make this
> update if anyone wants to talk to me about what I need to do in order to do
> so.
>
> thanks
> Iain
>
> On Thu, Jan 5, 2012 at 9:16 AM, Iain Duncan <iainduncanlists@gmail.com>
> wrote:
>>
>> Thanks guys. Don't you think both of these answers should be included in
>> the manual page I referenced? I don't mind updating it if I have access to
>> that and someone tells me the procedure. And double checks my changes I
>> guess.
>>
>> iain
>>
>> On Thu, Jan 5, 2012 at 1:36 AM, Victor Lazzarini
>> <Victor.Lazzarini@nuim.ie> wrote:
>>>
>>> My impression is that both will work. makePlugin() calls SharedLibrary.
>>>
>>> Victor
>>> On 5 Jan 2012, at 04:16, Iain Duncan wrote:
>>>
>>> Hi folks, I'd be happy to update it if no one else wants to, though not
>>> sure what the deal is these days with access to sources.
>>>
>>> It looks like this page:
>>> http://www.csounds.com/manual/html/csound5extending.html
>>>
>>> has a confusing or out of date section here:
>>>
>>> (begin quote)
>>> Add your plugin as a new target in the plugin opcodes section of the
>>> SConstruct build file:
>>>
>>> pluginEnvironment.SharedLibrary('newgen',
>>> Split('''Opcodes/newgen.c
>>> Opcodes/another_file_used_by_newgen.c
>>> Opcodes/yet_another_file_used_by_newgen.c'''))
>>>
>>> (end quote)
>>>
>>> When I look in Sconstruct, I don't see any other instances of
>>> "pluginEnvironment.SharedLibrary", and all I seemed to have to do to add my
>>> opcode was add:
>>>
>>> makePlugin(pluginEnvironment, 'myop', ['Opcodes/myop.c'])
>>>
>>> Go coconut walky-talkies! cargo cult programming in action.... if someone
>>> can verify that this is indeed the proper way to land the planes with my
>>> coconuts, I'd be happy to update the manual. But I really have no idea what
>>> I'm doing there, beyond imitating what seems to be already there.
>>>
>>> Thanks!
>>> Iain
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>>> infrastructure or vast IT resources to deliver seamless, secure access to
>>> virtual desktops. With this all-in-one solution, easily deploy virtual
>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>>> costs. Try it free!
>>> http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> Dr Victor Lazzarini
>>> Senior Lecturer
>>> Dept. of Music
>>> NUI Maynooth Ireland
>>> tel.: +353 1 708 3545
>>> Victor dot Lazzarini AT nuim dot ie
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>>> infrastructure or vast IT resources to deliver seamless, secure access to
>>> virtual desktops. With this all-in-one solution, easily deploy virtual
>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel