Hi Istvan,

After thinking about it, I think it is enough to have the symlink in
/usr/local/lib and don't need it in /usr/local/lib/csound/java.  The
reason I think this is that a user will download the package and
install, and if they want to work with csnd.jar then they won't have
to do anything with -Djava.library.path as the .so will be found when
java loads in /usr/local/lib.  So everything would be set up.  The
user if they want to distribute the program will likely package in
csnd.jar with their program for compilation purposes as well as making
it easier to define the classpath when distributing, but then require
that lib_csnd.so be installed by the user, which would be fine.  I
think that is reasonable.

steven


> I already install lib_csnd.so to /usr/local/lib (with a symbolic link as
> /usr/lib/python2.4/lib-dynload/_csnd.so, but that is not relevant here),
> so no additional changes are needed for that. However, do you suggest
> creating a symbolic link in /usr/local/lib/csound/java as well ?


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net