If libturbojpeg.jnilib is not found on Mac systems, specifically look for it under /usr/lib, since /usr/lib isn't part of the default java.library.path on that platform.
git-svn-id: svn+ssh://svn.code.sf.net/p/libjpeg-turbo/code/trunk@861 632fc199-4ca6-4c93-a231-07263d6284db
diff --git a/java/README b/java/README
index 22e0f73..8bca071 100644
--- a/java/README
+++ b/java/README
@@ -34,22 +34,10 @@
pre-allocating the buffers is recommended.
-Note for OS X users
--------------------
-
-/usr/lib, the directory under which libturbojpeg.dylib is installed on Mac
-systems, is not part of the normal Java library path. Thus, when running a
-Java application that uses TurboJPEG/OSS on Mac systems, you will need to pass
-an argument of -Djava.library.path=/usr/lib to java.
-
-
-Note for Solaris users
+Installation Directory
----------------------
-/opt/libjpeg-turbo/lib, the directory under which libturbojpeg.so is installed
-on Solaris systems, is not part of the normal Java library path. Thus, when
-running a Java application that uses TurboJPEG/OSS on Solaris systems, you will
-need to pass an argument of -Djava.library.path=/opt/libjpeg-turbo/lib to java.
-If using a 64-bit data model, then instead pass an argument of
--Djava.library.path=/opt/libjpeg-turbo/lib/amd64 to use the 64-bit version of
-libturbojpeg.so.
+If the TurboJPEG JNI library (libturbojpeg.so, libturbojpeg.jnilib, or
+turbojpeg.dll) is not installed under a system library directory or under a
+directory specified in LD_LIBRARY_PATH (Unix) or PATH (Windows), then you will
+need to pass an argument of -Djava.library.path={path_to_JNI_library} to java.