The extension is generally .dylib, but it does not really matter. You  
can leave it in the same directory as your CSD and then load
it with the option --opcode-lib=libname

That is the best way of testing/using custom opcodes.

Victor
On 21 May 2011, at 15:03, Alex Weiss wrote:

> Hello list,
>
> Forgive my ignorance, but where am I to put custom opcodes (.so  
> files) on an OS X system? I'm working on an opcode that I'd like to  
> test.
>
> Thanks.
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
> 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




------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Just to add to Victor's reply, the OPCODEDIR and OPCODEDIR64 default
on OSX to /Library/Frameworks/CsoundLib.framework/Versions/5.2/Resources/opcodes
and /Library/Frameworks/CsoundLib64.framework/Versions/5.2/Resources/Opcodes64
respectively.  I'd follow Victor's advice; however, if you want to
have those opcodes available without specifying --opcode-lib= you can
drop it into one of those directories depending on if it's built for
float/double.

 steven

On Sat, May 21, 2011 at 10:14 AM, Victor Lazzarini
 wrote:
> The extension is generally .dylib, but it does not really matter. You
> can leave it in the same directory as your CSD and then load
> it with the option --opcode-lib=libname
>
> That is the best way of testing/using custom opcodes.
>
> Victor
> On 21 May 2011, at 15:03, Alex Weiss wrote:
>
>> Hello list,
>>
>> Forgive my ignorance, but where am I to put custom opcodes (.so
>> files) on an OS X system? I'm working on an opcode that I'd like to
>> test.
>>
>> Thanks.
>> ------------------------------------------------------------------------------
>> What Every C/C++ and Fortran developer Should Know!
>> Read this article and learn how Intel has extended the reach of its
>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>> developers boost performance applications - including clusters.
>> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
>> 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
>
>
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thank you, Victor and Steven. Is there a way to make csound's loading mechanism more verbose? Csound can't find my opcode, so I assume loading the dylib failed. But I have no way to tell, since I don't get an error message during loading.

On Sat, May 21, 2011 at 4:20 PM, Steven Yi <stevenyi@gmail.com> wrote:

Just to add to Victor's reply, the OPCODEDIR and OPCODEDIR64 default
on OSX to /Library/Frameworks/CsoundLib.framework/Versions/5.2/Resources/opcodes
and /Library/Frameworks/CsoundLib64.framework/Versions/5.2/Resources/Opcodes64
respectively.  I'd follow Victor's advice; however, if you want to
have those opcodes available without specifying --opcode-lib= you can
drop it into one of those directories depending on if it's built for
float/double.

 steven

On Sat, May 21, 2011 at 10:14 AM, Victor Lazzarini
<Victor.Lazzarini@nuim.ie> wrote:
> The extension is generally .dylib, but it does not really matter. You
> can leave it in the same directory as your CSD and then load
> it with the option --opcode-lib=libname
>
> That is the best way of testing/using custom opcodes.
>
> Victor
> On 21 May 2011, at 15:03, Alex Weiss wrote:
>
>> Hello list,
>>
>> Forgive my ignorance, but where am I to put custom opcodes (.so
>> files) on an OS X system? I'm working on an opcode that I'd like to
>> test.
>>
>> Thanks.
>> ------------------------------------------------------------------------------
>> What Every C/C++ and Fortran developer Should Know!
>> Read this article and learn how Intel has extended the reach of its
>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>> developers boost performance applications - including clusters.
>> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
>> 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
>
>
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay

_______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel

For automatic loading to work, on OSX opcodes need to have the dylib  
extension.  That does not matter for --opcode-lib=

Victor
On 21 May 2011, at 15:20, Steven Yi wrote:

> Just to add to Victor's reply, the OPCODEDIR and OPCODEDIR64 default
> on OSX to /Library/Frameworks/CsoundLib.framework/Versions/5.2/ 
> Resources/opcodes
> and /Library/Frameworks/CsoundLib64.framework/Versions/5.2/Resources/ 
> Opcodes64
> respectively.  I'd follow Victor's advice; however, if you want to
> have those opcodes available without specifying --opcode-lib= you can
> drop it into one of those directories depending on if it's built for
> float/double.
>
> steven
>
> On Sat, May 21, 2011 at 10:14 AM, Victor Lazzarini
>  wrote:
>> The extension is generally .dylib, but it does not really matter. You
>> can leave it in the same directory as your CSD and then load
>> it with the option --opcode-lib=libname
>>
>> That is the best way of testing/using custom opcodes.
>>
>> Victor
>> On 21 May 2011, at 15:03, Alex Weiss wrote:
>>
>>> Hello list,
>>>
>>> Forgive my ignorance, but where am I to put custom opcodes (.so
>>> files) on an OS X system? I'm working on an opcode that I'd like to
>>> test.
>>>
>>> Thanks.
>>> ------------------------------------------------------------------------------
>>> What Every C/C++ and Fortran developer Should Know!
>>> Read this article and learn how Intel has extended the reach of its
>>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>>> developers boost performance applications - including clusters.
>>> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
>>> 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
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What Every C/C++ and Fortran developer Should Know!
>> Read this article and learn how Intel has extended the reach of its
>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>> developers boost performance applications - including clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> 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




------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Ah, yes, I missed that part about .so in the original email. :)

On Sat, May 21, 2011 at 12:48 PM, Victor Lazzarini
 wrote:
> For automatic loading to work, on OSX opcodes need to have the dylib
> extension.  That does not matter for --opcode-lib=
>
> Victor
> On 21 May 2011, at 15:20, Steven Yi wrote:
>
>> Just to add to Victor's reply, the OPCODEDIR and OPCODEDIR64 default
>> on OSX to /Library/Frameworks/CsoundLib.framework/Versions/5.2/
>> Resources/opcodes
>> and /Library/Frameworks/CsoundLib64.framework/Versions/5.2/Resources/
>> Opcodes64
>> respectively.  I'd follow Victor's advice; however, if you want to
>> have those opcodes available without specifying --opcode-lib= you can
>> drop it into one of those directories depending on if it's built for
>> float/double.
>>
>> steven
>>
>> On Sat, May 21, 2011 at 10:14 AM, Victor Lazzarini
>>  wrote:
>>> The extension is generally .dylib, but it does not really matter. You
>>> can leave it in the same directory as your CSD and then load
>>> it with the option --opcode-lib=libname
>>>
>>> That is the best way of testing/using custom opcodes.
>>>
>>> Victor
>>> On 21 May 2011, at 15:03, Alex Weiss wrote:
>>>
>>>> Hello list,
>>>>
>>>> Forgive my ignorance, but where am I to put custom opcodes (.so
>>>> files) on an OS X system? I'm working on an opcode that I'd like to
>>>> test.
>>>>
>>>> Thanks.
>>>> ------------------------------------------------------------------------------
>>>> What Every C/C++ and Fortran developer Should Know!
>>>> Read this article and learn how Intel has extended the reach of its
>>>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>>>> developers boost performance applications - including clusters.
>>>> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
>>>> 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
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> What Every C/C++ and Fortran developer Should Know!
>>> Read this article and learn how Intel has extended the reach of its
>>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>>> developers boost performance applications - including clusters.
>>> http://p.sf.net/sfu/intel-dev2devmay
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> What Every C/C++ and Fortran developer Should Know!
>> Read this article and learn how Intel has extended the reach of its
>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>> developers boost performance applications - including clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> 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
>
>
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

not sure if this can help, but there is an option -v for verbose console
output.
	joachim

Am 21.05.2011 16:34, schrieb Alex Weiss:
> Thank you, Victor and Steven. Is there a way to make csound's loading
> mechanism more verbose? Csound can't find my opcode, so I assume loading
> the dylib failed. But I have no way to tell, since I don't get an error
> message during loading.
> 
> On Sat, May 21, 2011 at 4:20 PM, Steven Yi  > wrote:
> 
>     Just to add to Victor's reply, the OPCODEDIR and OPCODEDIR64 default
>     on OSX to
>     /Library/Frameworks/CsoundLib.framework/Versions/5.2/Resources/opcodes
>     and
>     /Library/Frameworks/CsoundLib64.framework/Versions/5.2/Resources/Opcodes64
>     respectively.  I'd follow Victor's advice; however, if you want to
>     have those opcodes available without specifying --opcode-lib= you can
>     drop it into one of those directories depending on if it's built for
>     float/double.
> 
>      steven
> 
>     On Sat, May 21, 2011 at 10:14 AM, Victor Lazzarini
>     > wrote:
>     > The extension is generally .dylib, but it does not really matter. You
>     > can leave it in the same directory as your CSD and then load
>     > it with the option --opcode-lib=libname
>     >
>     > That is the best way of testing/using custom opcodes.
>     >
>     > Victor
>     > On 21 May 2011, at 15:03, Alex Weiss wrote:
>     >
>     >> Hello list,
>     >>
>     >> Forgive my ignorance, but where am I to put custom opcodes (.so
>     >> files) on an OS X system? I'm working on an opcode that I'd like to
>     >> test.
>     >>
>     >> Thanks.
>     >>
>     ------------------------------------------------------------------------------
>     >> What Every C/C++ and Fortran developer Should Know!
>     >> Read this article and learn how Intel has extended the reach of its
>     >> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>     >> developers boost performance applications - including clusters.
>     >>
>     http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
>     >> 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
>     >
>     >
>     >
>     >
>     >
>     ------------------------------------------------------------------------------
>     > What Every C/C++ and Fortran developer Should Know!
>     > Read this article and learn how Intel has extended the reach of its
>     > next-generation tools to help Windows* and Linux* C/C++ and Fortran
>     > developers boost performance applications - including clusters.
>     > http://p.sf.net/sfu/intel-dev2devmay
>     > _______________________________________________
>     > Csound-devel mailing list
>     > Csound-devel@lists.sourceforge.net
>     
>     > https://lists.sourceforge.net/lists/listinfo/csound-devel
>     >
> 
>     ------------------------------------------------------------------------------
>     What Every C/C++ and Fortran developer Should Know!
>     Read this article and learn how Intel has extended the reach of its
>     next-generation tools to help Windows* and Linux* C/C++ and Fortran
>     developers boost performance applications - including clusters.
>     http://p.sf.net/sfu/intel-dev2devmay
>     _______________________________________________
>     Csound-devel mailing list
>     Csound-devel@lists.sourceforge.net
>     
>     https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its 
> next-generation tools to help Windows* and Linux* C/C++ and Fortran 
> developers boost performance applications - including clusters. 
> http://p.sf.net/sfu/intel-dev2devmay
> 
> 
> 
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net