From 4b53f5582733c35c526ed36e108ae65a8b8d50e5 Mon Sep 17 00:00:00 2001 From: Hans-Christian Egtvedt Date: Thu, 10 Apr 2014 17:51:45 +0200 Subject: [PATCH] INSTALL: add cross compile and install procedures for Android This patch adds some words in the INSTALL file about how to cross compile some utilities (compliance, ctl, and dbg) for Android and install the on a device running Android. Signed-off-by: Hans-Christian Egtvedt Signed-off-by: Hans Verkuil --- INSTALL | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/INSTALL b/INSTALL index 6caa0f2..a26e1a0 100644 --- a/INSTALL +++ b/INSTALL @@ -44,3 +44,30 @@ export PKG_CONFIG_LIBDIR=/path/to/cross/root/lib ./configure --host=arm-linux-gnueabihf --without-jpeg make +Android Cross Compiling and Installing: +---------------- + +v4l-utils will only build using the complete AOSP source tree, because of the +stlport dependency. + +List of v4l-utils that supply an Android.mk makefile: +* utils/v4l2-compliance +* utils/v4l2-ctl +* utils/v4l2-dbg + +To cross compile an utility you must first configure the shell with Android's +envsetup.sh to add the mm alias, before running lunch to select your target +device. + +cd /path/to/aosp +source build/envsetup.sh +lunch +cd /path/to/v4l-utils +cd +mm + +Output binary will be located in the Android out directory, below the +target/product//system/bin/ path. + +The binary executable can be pushed to the target Android device using +adb push /system/bin -- 2.7.4