[FE training-materials-updates] Fix wrapping in the libusb slides

Maxime Ripard maxime.ripard at free-electrons.com
Thu Mar 21 16:50:30 CET 2013


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

On branch  : various-fixes
Link       : http://git.free-electrons.com/training-materials/commit/?id=fde0718d2a65d26e157913621abc1c0add32cc46

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

commit fde0718d2a65d26e157913621abc1c0add32cc46
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Thu Mar 21 11:13:48 2013 +0100

    Fix wrapping in the libusb slides
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

fde0718d2a65d26e157913621abc1c0add32cc46
 .../android-native-library.tex                     |   44 ++++++++++----------
 1 file changed, 23 insertions(+), 21 deletions(-)

diff --git a/labs/android-native-library/android-native-library.tex b/labs/android-native-library/android-native-library.tex
index c480801..fc9be6a 100644
--- a/labs/android-native-library/android-native-library.tex
+++ b/labs/android-native-library/android-native-library.tex
@@ -9,34 +9,36 @@ After this lab, you will be able to
 
 \section{Building a static library}
 
-To get the libusb source code, go to \url{http://libusb.org} and download
-version 1.0.9. Extract the archive in the \code{external/libusb} folder.
+To get the libusb source code, go to \url{http://libusb.org} and
+download version 1.0.9. Extract the archive in the
+\code{external/libusb} folder.
 
-For this library, all the needed \code{.c} files are located in the \code{libusb}
-folder and its subfolders. The headers are located in the same folders. Make
-the build system generate a \code{libusb-static.a} file.
+For this library, all the needed \code{.c} files are located in the
+\code{libusb} folder and its subfolders. The headers are located in
+the same folders. Make the build system generate a
+\code{libusb-static.a} file.
 
-You will find one missing header that you will need to generate. Indeed, the
-\code{config.h} generated by autoconf is not generated at all, because the
-Android build system ignores other build systems. You will have to generate it
-by yourself.
+You will find one missing header that you will need to
+generate. Indeed, the \code{config.h} generated by autoconf is not
+generated at all, because the Android build system ignores other build
+systems. You will have to generate it by yourself.
 
-If successful, the build system should go through the build process and you
-should have a directory generated in the \code{out} directory.
+If successful, the build system should go through the build process
+and you should have a directory generated in the \code{out} directory.
 
 \section{Building a shared library}
 
-Now, we will need to build a shared library along with the static one, called
-\code{libusb.so}. Use the same \code{config.h} and modify the \code{Android.mk}
-file so that it gets compiled. Then, check that the shared object is present in
-the \code{out} folder.
+Now, we will need to build a shared library along with the static one,
+called \code{libusb.so}. Use the same \code{config.h} and modify the
+\code{Android.mk} file so that it gets compiled. Then, check that the
+shared object is present in the \code{out} folder.
 
 \section{Integrate the library into the Android image}
 
-As you can see, your library has been compiled during the build process, but if
-you boot the generated image or look inside the
-\code{out/target/product/training/system/lib}
-folder, you can see that the shared object is not present.
+As you can see, your library has been compiled during the build
+process, but if you boot the generated image or look inside the
+\code{out/target/product/training/system/lib} folder, you can see that
+the shared object is not present.
 
-Modify the appropriate files so that in the images, you will have the two 
-variants of the library we compiled.
+Modify the appropriate files so that in the images, you will have the
+two variants of the library we compiled.



More information about the training-materials-updates mailing list