Modify build instructions to reflect the fact that the Java front-end classes are...

git-svn-id: svn+ssh://svn.code.sf.net/p/libjpeg-turbo/code/trunk@551 632fc199-4ca6-4c93-a231-07263d6284db

diff --git a/BUILDING.txt b/BUILDING.txt
index 0af9fdf29e7996ae071cebe6a49208f56de0be21..86ca1c99dcd7dbd202f07ce42690bcbdeeae0806 100644 (file)
--- a/BUILDING.txt
+++ b/BUILDING.txt
@@ -126,10 +126,18 @@ disable encoding or decoding (respectively.)
 
 TurboJPEG/OSS JNI Wrapper
 -------------------------
-Add --with-jni to the configure command line to incorporate an optional Java
-Native Interface wrapper into the TurboJPEG/OSS dynamic library.  This allows
-the dynamic library to be used directly from Java applications.  See
-java/README for more details.
+Add --with-java to the configure command line to incorporate an optional Java
+Native Interface wrapper into the TurboJPEG/OSS dynamic library and build the
+Java front-end classes to support it.  This allows the TurboJPEG/OSS dynamic
+library to be used directly from Java applications.  See java/README for more
+details.
+
+You can set the JAVAC, JAR, and JAVA configure variables to specify
+alternate commands for javac, jar, and java (respectively.)  You can also
+set the JAVACFLAGS configure variable to specify arguments that should be
+passed to the Java compiler when building the front-end classes, and JNI_CFLAGS
+to specify arguments that should be passed to the C compiler when building the
+JNI wrapper.  Run 'configure --help' for more details.
 
 
 ========================