[FE training-materials-updates] Use the app_process command line to avoid the println_native linking error

[Maxime Ripard]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=f9ce3390c75ae91f7103ea6f5af44190664efe22

>---------------------------------------------------------------

commit f9ce3390c75ae91f7103ea6f5af44190664efe22
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Mon Oct 1 15:29:27 2012 +0200

    Use the app_process command line to avoid the println_native linking error
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


>---------------------------------------------------------------

f9ce3390c75ae91f7103ea6f5af44190664efe22
 labs/android-jni-library/android-jni-library.tex |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/labs/android-jni-library/android-jni-library.tex b/labs/android-jni-library/android-jni-library.tex
index 46119a4..ec24e8b 100644
--- a/labs/android-jni-library/android-jni-library.tex
+++ b/labs/android-jni-library/android-jni-library.tex
@@ -45,8 +45,10 @@ classes, \code{/system/lib/liblauncher_jni.so}, containing the JNI bindings and
 \code{/system/lib/libusb.so}.
 
 Test what you did using the Main class present in the Java source code
-by directly invoking Dalvik through the \code{dalvikvm} command. You
-will have to provide both the classpath and the class name to make it work.
+by directly invoking Dalvik through the \code{app_process}
+command. You will have to provide both the classpath and the class
+name to make it work and should look like
+\code{CLASSPATH=path/to/java.jar app_process /system/bin com.fe.android.Main}
 
 Once you have a solution that works, you can ask your instructor to 
 give you a URL where Free Electrons' solution is available, and compare