FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 299 : Processing 107 :: no QTJava in java.library.path
Last modified: 2006-03-23 19:55
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
FIXED -
Pr
i
ority:
P2
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
smallfly
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2006-03-06 06:35
Windows XP + Processing 101 expert + jdk1.5.0_06 & jre1.5.0_06 + winVDIG
1.0.1 + QuickTime 7 = Everything works.
Windows XP + Processing 107 expert + jdk1.5.0_06 & jre1.5.0_06 + winVDIG
1.0.1 + QuickTime 7 = "no QTJava in java.library.path".
In my "system properties"/env. variables I have :
CLASSPATH = C:\Program Files\Java\jre1.5.0_06\lib\ext\QTJava.zip
and
QTJava = C:\Program Files\Java\jre1.5.0_06\lib\ext\QTJava.zip
And in a cmd window:
echo %PATH%
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Prog
ve Software\Diskeeper\;C:\Program Files\ATI Technologies\ATI.AC
es\Common Files\Adobe\AGL
and
echo %CLASSPATH%
C:\Program Files\Java\jre1.5.0_06\lib\ext\QTJava.zip
I also tried this (in Processing):
println(System.getProperty("java.library.path"));
with Processing 101 I get:
;D:\Processing\processing-0101-expert\libraries\video\library;C:\WINDOWS
\system32;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOW
S;C:\WINDOWS\System32\Wbem;C:\Program Files\Executive
Software\Diskeeper\;C:\Program Files\ATI Technologies\ATI.ACE\;C:\Program
Files\Common Files\Adobe\AGL;C:\Program Files\QuickTime\QTSystem\
with Processing 107 I get:
;D:\Processing\processing-0107-expert\libraries\video\library;C:\WINDOWS
\system32;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOW
S;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\Adobe\AGL
Additional Comment
#1 From fry 2006-03-06 07:59
this looks to me as though the newer processing.exe in 107 doesn't like the paths that have
spaces, or doesn't like the trailing slash. i'll need to make a special version of processing.exe
for you to test this out and will also look at the code to see what i can find.
Additional Comment
#2 From fry 2006-03-21 14:11
confirmed that the problem is trailing slashes in path names. fixed with a
new exe that removes the trailing slashes for 0109.
Additional Comment
#3 From smallfly 2006-03-23 19:55
I have tested on my machine and it works ! Thanks !