On Feb 26, 2008, at 11:31 AM, shu fan wrote:
I am also a user of jna. Actually I had the same problem as the
issue post on website. I tried the solution – unarchived
jnidispatch.dll to where system.loadlibrary() can find.
Unfortunately, the problem still exists, and plenty of jnaxxxx.dll
are created in the temp directory and never deleted.
I thought you have already solved this problem perfectly, thus I
wrote to ask for help. Could you please give me the very detail
that how you get rid of those jna temp dlls.
What version of JNA are you using? "java -jar jna.jar" will tell you.
On my XP Pro system, the generated filenames are jnaxxxx.tmp, not
jnaxxxx.dll.
Write a short test in Java which does
System.loadLibrary("jnidispatch"). Make sure that works
(jnidispatch.dll must be found in PATH). If not, the JNA load won't
work either.
Write a short test which prints the value of
System.getProperty("java.io.tmpdir"). This is where the jna temp file
will be written, and may or may not correspond to the TEMP or TMP
environment variable.
If your program crashes for any reason (or is terminated from within a
debugger), it will prevent the temp file from being removed.
1 message in net.java.dev.jna.usersRe: jna temp dll
