[Bluemusic-users] Fix found
Brought to you by:
kunstmusik
From: Steven Yi <ste...@gm...> - 2005-05-13 03:57:06
|
Hi Hector and all, I figured out what the problem was, and it makes no sense. =3Do =20 So, a few versions ago I switched from putting the classpath information in the starter script to putting it in the jar file with a manifest. That technically should have absolutely no problems, but it did, and I never realized as I was using an older version of the script floating around on my system. So... the thing to do is replace the contents of blue.sh with: BLUE_HOME=3D/home/steven/workspace/blue BLUE_LIBS=3D$BLUE_HOME/lib/java-getopt-1.0.9.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/blue.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/jython.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/EXML.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/js.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/xmlrpc-1.1.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/jacl.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/tcljava.jar BLUE_LIBS=3D$BLUE_LIBS:$BLUE_HOME/lib/l2fprod-common-sheet.jar java -DBLUE_HOME=3D"$BLUE_HOME" -cp $BLUE_LIBS blue.Blue "$@" Just change BLUE_HOME to /usr/local/blue or wherever you have that set. After doing that, try running the projects you had problems with. I noticed something strange where I sometimes had problems after using this script when before using the manifest version that I would still get errors until I did a "test" on one of the Python soundObjects, then everything worked again. I've switched the scripts back to old versions. I'll push another release out shortly... Sorry about that! =3Do steven |