On Tue, 18 Aug 2009, Andi Vajda wrote:
Maybe the JVM is depending on some native code that can't be found for this class. In that case you'd need to use -Djava.library.path=<path> with vmargs. If that resolves the problem, adding another command line flag to jcc for setting the library path should be considered.
I added a new parameter, --libpath, that makes it possible to set java.library.path in vmargs from the command line.
This is committed in rev 806057. Andi..
