[FE training-materials-updates] Mention how to generate the libusb config.h file

Maxime Ripard maxime.ripard at free-electrons.com
Thu Mar 21 16:50:32 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=3cf016af935970d0550a3551c47e7e514ef00d9a


commit 3cf016af935970d0550a3551c47e7e514ef00d9a
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Thu Mar 21 11:17:29 2013 +0100

    Mention how to generate the libusb config.h file
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


 .../android-native-library.tex                     |    6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/labs/android-native-library/android-native-library.tex b/labs/android-native-library/android-native-library.tex
index fc9be6a..7bb9957 100644
--- a/labs/android-native-library/android-native-library.tex
+++ b/labs/android-native-library/android-native-library.tex
@@ -21,7 +21,11 @@ the same folders. Make the build system generate a
 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.
+systems. You will have to generate it by yourself, by running the
+\code{configure} script \footnote{You can have some hints about the
+  available options available by passing the \code{--help} argument to
+  \code{configure}} that you can find in the \code{libusb} source
 If successful, the build system should go through the build process
 and you should have a directory generated in the \code{out} directory.

More information about the training-materials-updates mailing list