Yes, ignoring the variables. As for the directory, we can
use
/usr/local/lib/plugin etc. I am thinking here of multi-user
systems,
where things can be accessed by more than one user. This is
what I meant by system-wide environment variables, set for
all users.

Another option is to install Csound as a framework, on
System/Libraries/Frameworks/Csound.Framework and
put the plugin directory in there.

Victor

>
> Victor Lazzarini wrote:
>
> > In relation to environment variables, mainly OPCODEDIR
> > and OPCODEDIR64, I am thinking that on OSX, I will
> > probably suggest a hardcoding of these directories. The
> > reason is that, unlik on Windows and lInux, there is no
> > way of setting a system-wide environment variable. It is
> > possible to do it for the terminal, but not for Apps
> launched by Finder/Acqua. Is there any
>  > problem with doing this?
>
> Do you mean ignoring OPCODEDIR/OPCODEDIR64 completely on
> OS X, or having an absolute path instead of "." as the
> default ? Also, what directories do you suggest ?
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get
> Certified Today Register for a JBoss Training Course.
> Free Certification Exam for All Training Attendees Through
> End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net