[FE training-materials-updates] Add details about the PATH and the emulator

[michael.opdenacker at free-electrons.com]

- Log -----------------------------------------------------------------
http://git.free-electrons.com/training-materials/commit/?id=4f75e40051db6916aa5f6e52f8953ee9f6334b1b

commit 4f75e40051db6916aa5f6e52f8953ee9f6334b1b
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Tue Jun 5 10:39:16 2012 +0200

    Add details about the PATH and the emulator

diff --git a/labs/android-first-compilation/android-first-compilation.tex b/labs/android-first-compilation/android-first-compilation.tex
index 68acdcd..84adebc 100644
--- a/labs/android-first-compilation/android-first-compilation.tex
+++ b/labs/android-first-compilation/android-first-compilation.tex
@@ -27,7 +27,7 @@ Check your \code{PATH} environment variable:
 echo $PATH
 \end{verbatim}
 
-You will see that  \code{build/envsetup.sh} hasn't modified your \code{PATH}.
+You will see that \code{build/envsetup.sh} hasn't modified your \code{PATH}.
 This will be done during the build job.
 
 The target product for the emulator is {\it generic}, and we want to have an 
@@ -56,8 +56,7 @@ the double number of parallel jobs:
 make -j 8
 \end{verbatim}
 
-Go grab (several cups of) coffee, and you will have the system compiled in three
-images in the \code{out/target/product/generic} folder.
+Go grab (several cups of) coffee!
 
 \textbf{Known issue}: in rare circumstances, some builds can fail when \code{make}
 is run with multiple jobs in parallel. If this happens, you can run \code{make}
@@ -65,9 +64,28 @@ with no option after the failure, and this is likely to make the issue disappear
 
 \section{Test your Android build}
 
-Now, look at the \code{PATH} environment variable again. It should now contain
-extra directories with new binaries produced by the build job.
+Now, look at the \code{PATH} environment variable again.
 
-Run the \code{emulator} command. It will run the emulator with the newly generated images.
+You can see that it contains:
+\begin{itemize}
+   \item \code{$HOME/felabs/android/aosp/android/out/host/linux-x86/bin/}.
+   That's where new utilities have just been compiled.
+   \item Prebuilt executables, in particular the ARM cross-compiling toolchain,
+   which was already present in the repositories fetched by \code{repo}.
+\end{itemize}
+
+Look at the contents of the \code{out/target/product/generic} folder.
+That's where the system images have been built.
+
+Run the \code{emulator} command. It will run the emulator with these generated images.
 Wait a few minutes for the emulator to load the system, and then 
-check the build version in the \code{Settings} application in Android.
+check the build number in the \code{Settings} application in Android.
+
+\textbf{Tip}: the \code{PATH} settings automatically added by the build
+process will be lost if you close your terminal. To access the emulator
+from another session, you will have
+to set your \code{PATH} manually: 
+
+\begin{verbatim}
+PATH=$PATH:$HOME/felabs/android/aosp/android/out/host/linux-x86/bin/
+\end{verbatim}

-----------------------------------------------------------------------

Summary of changes:
 .../android-first-compilation.tex                  |   32 +++++++++++++++-----
 1 file changed, 25 insertions(+), 7 deletions(-)