Hi,
As more and more Java programs use JNA (FileBot, Processing, etc) and install themselves into the PATH (e.g. FileBot) other arbitrary other tools (e.g. Processing) that don't have -Djna.nosys=true set correctly will break.
Most JNA developer just use it, and think the libraries will be unpacked from the jar, and most don't even know that JNA will actually prefer any jnidispatch.dll that's in the PATH. Only FileBot correctly sets jna.nosys=true while almost any other tool using JNA is oblivious of this issue.
Setting -Djna.nosys=true by default would force the correct default behavior that is assumed by most JNA users anyway already.
Thoughts?
PS: this is probably only an issue on Windows
Hi,
As more and more Java programs use JNA (FileBot, Processing, etc) and install themselves into the PATH (e.g. FileBot) other arbitrary other tools (e.g. Processing) that don't have -Djna.nosys=true set correctly will break.
Most JNA developer just use it, and think the libraries will be unpacked from the jar, and most don't even know that JNA will actually prefer any jnidispatch.dll that's in the PATH. Only FileBot correctly sets jna.nosys=true while almost any other tool using JNA is oblivious of this issue.
Setting -Djna.nosys=true by default would force the correct default behavior that is assumed by most JNA users anyway already.
Thoughts?
PS: this is probably only an issue on Windows