Hi,
what I know about the csound plugin libraries is that (please correct me 
if I am wrong):

 - Plugin libraries are loaded from the directory defined by the 
environment  variable OPCODEDIR (or the current directory if OPCODEDIR 
is unset)

 So is it correct that there is no mechanism for looking into 
/usr/lib/csound/plugins or /usr/local/lib/csound/plugins as well if 
there are plugins without specifying the OPCODEDIR?

When building a binary package where I install into /usr/csound/plugins 
for example do I need to set the env variable as well in order to make 
it work for the user?

Thanks,
   Simon

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven Yi wrote:
> Hi Simon,
>
> For the OPCODEDIR stuff, just to clarify, it will be OPCODEDIR if it
> is a float build and OPCODEDIR64 if it is a double build.  Also, the
> default is the current working directory only if it is not a release
> build.  You can see the relevant code in InOut/csmodule.c.
>
> /* default directory to load plugins from if environment variable is not set */
> #if !(defined(_CSOUND_RELEASE_) && (defined(LINUX) || defined(__MACH__)))
> #  define ENABLE_OPCODEDIR_WARNINGS 1
> #  ifdef CS_DEFAULT_PLUGINDIR
> #    undef CS_DEFAULT_PLUGINDIR
> #  endif
> #  define CS_DEFAULT_PLUGINDIR      "."
> #else
> #  define ENABLE_OPCODEDIR_WARNINGS 0
> #  ifndef CS_DEFAULT_PLUGINDIR
> #    ifndef USE_DOUBLE
> #      define CS_DEFAULT_PLUGINDIR  "/usr/local/lib/csound/plugins"
> #    else
> #      define CS_DEFAULT_PLUGINDIR  "/usr/local/lib/csound/plugins64"
> #    endif
> #  endif
> #endif
>
> It looks like you define CS_DEFAULT_PLUGINDIR and buildRelease=1, then
> you can at build time change what the default directory will be.
>
>   
Hi Steven & others,
thanks for your replys. This note was what I am looking and which worked 
for me at the moment. I wanted a  solution where the setting of the env 
variable would not be required.
> Otherwise, you'll have to set the env variable at the user side.  I've
> noticed on Fedora that a number of packages do this by installing a
> shell script to the /etc/profile.d directory, and I think then that if
> users define that in .bashrc, it will override the value in
> /etc/profile.d.
>
> Hope that helps!
> steven
>
>
>   

Right, the environment variables which are set in /etc/profile.d are for 
all the users except root.
Thanks,
   Simon

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net