Comments on: Modify java.library.path at runtime http://nicklothian.com/blog/2008/11/19/modify-javalibrarypath-at-runtime/ My Blog, Take 4 Tue, 06 Jan 2009 22:11:32 +0000 http://wordpress.org/?v=2.6.5 By: Nick Lothian http://nicklothian.com/blog/2008/11/19/modify-javalibrarypath-at-runtime/#comment-503 Nick Lothian Thu, 20 Nov 2008 22:20:50 +0000 http://nicklothian.com/blog/?p=335#comment-503 Yes, that would normally be the sensible thing to do. However, in this case I was using a pre-packaged library (JNotify), which used System.loadLibrary(String), and so required the library to be on the library path. Yes, that would normally be the sensible thing to do. However, in this case I was using a pre-packaged library (JNotify), which used System.loadLibrary(String), and so required the library to be on the library path.

]]> By: svenmeier http://nicklothian.com/blog/2008/11/19/modify-javalibrarypath-at-runtime/#comment-502 svenmeier Thu, 20 Nov 2008 12:35:27 +0000 http://nicklothian.com/blog/?p=335#comment-502 I prefer loading native libs from a known place, e.g. a 'lib' subfolder or even better the directory of the jar, your class was loaded from. See System.load(String). I prefer loading native libs from a known place, e.g. a ‘lib’ subfolder or even better the directory of the jar, your class was loaded from.

See System.load(String).

]]>