Hi,

I made an Xcode template for making opcodes. It’ll set up the bare necessary opcode stuff, like a struct, init, process functions, and an opcode entries struct also. It makes a test csd, and also copies the opcode dylib into the csound opcode64 directory. This will work with the home-brew installed version of csound, I don’t know if it’ll work using the installer because correct me if I’m wrong does home-brew put CsoundLib64.framework in ~/Library/Frameworks and the installer uses /Library/Frameworks? I think I had trouble copying the dylib into the /Library/Frameworks directory. 
Anyway, if someone could test it, that would be great, you just need to copy the file into ~/Library/Developer/Xcode/Templates/Project Templates/GroupName, where GroupName could be ‘Csound’ or something like that. 
Cheers
Ed

Hi Ed,

I installed this and gave it a try. Pretty neat!  I didn't try
building/installing but you're right about the location of Frameworks.
If you build Csound with CMake or with homebrew, it will install the
framework into ~/Library/Frameworks.  The installer will install to
/Library/Frameworks.  I imagine you could add a custom build rule that
uses the equivalent of sudo to ask the user for permission to copy to
/Library/Frameworks.

Otherwise, everything was generated correctly. Also, I had not known
about designated initializers for initializing structs:

    {
        .opname = "MyOhMy",
        .dsblksiz = sizeof(MyOhMy),
        .thread = 3,
        .outypes = "",
        .intypes = "",
        .iopadr = (SUBR)MyOhMy_init,
        .kopadr = (SUBR)MyOhMy_process,
        .aopadr = NULL
    }

Nice!

Thanks!
steven


On Thu, Jul 24, 2014 at 6:34 AM, Edward Costello
 wrote:
> Hi,
>
> I made an Xcode template for making opcodes. It’ll set up the bare necessary opcode stuff, like a struct, init, process functions, and an opcode entries struct also. It makes a test csd, and also copies the opcode dylib into the csound opcode64 directory. This will work with the home-brew installed version of csound, I don’t know if it’ll work using the installer because correct me if I’m wrong does home-brew put CsoundLib64.framework in ~/Library/Frameworks and the installer uses /Library/Frameworks? I think I had trouble copying the dylib into the /Library/Frameworks directory.
> Anyway, if someone could test it, that would be great, you just need to copy the file into ~/Library/Developer/Xcode/Templates/Project Templates/GroupName, where GroupName could be ‘Csound’ or something like that.
> Cheers
> Ed
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://l

Good to hear its working ok, I’ll have a look and see if I can use sudo from Xcode’s build scripts and update the template if I get it working. 
Ed


On 24 Jul 2014, at 19:39, Steven Yi  wrote:

> Hi Ed,
> 
> I installed this and gave it a try. Pretty neat!  I didn't try
> building/installing but you're right about the location of Frameworks.
> If you build Csound with CMake or with homebrew, it will install the
> framework into ~/Library/Frameworks.  The installer will install to
> /Library/Frameworks.  I imagine you could add a custom build rule that
> uses the equivalent of sudo to ask the user for permission to copy to
> /Library/Frameworks.
> 
> Otherwise, everything was generated correctly. Also, I had not known
> about designated initializers for initializing structs:
> 
>    {
>        .opname = "MyOhMy",
>        .dsblksiz = sizeof(MyOhMy),
>        .thread = 3,
>        .outypes = "",
>        .intypes = "",
>        .iopadr = (SUBR)MyOhMy_init,
>        .kopadr = (SUBR)MyOhMy_process,
>        .aopadr = NULL
>    }
> 
> Nice!
> 
> Thanks!
> steven
> 
> 
> On Thu, Jul 24, 2014 at 6:34 AM, Edward Costello
>  wrote:
>> Hi,
>> 
>> I made an Xcode template for making opcodes. It’ll set up the bare necessary opcode stuff, like a struct, init, process functions, and an opcode entries struct also. It makes a test csd, and also copies the opcode dylib into the csound opcode64 directory. This will work with the home-brew installed version of csound, I don’t know if it’ll work using the installer because correct me if I’m wrong does home-brew put CsoundLib64.framework in ~/Library/Frameworks and the installer uses /Library/Frameworks? I think I had trouble copying the dylib into the /Library/Frameworks directory.
>> Anyway, if someone could test it, that would be great, you just need to copy the file into ~/Library/Developer/Xcode/Templates/Project Templates/GroupName, where GroupName could be ‘Csound’ or something like that.
>> Cheers
>> Ed
>> 
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
> 
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net