path: root/INSTALL
diff options
authorHans-Christian Egtvedt <hegtvedt@cisco.com>2014-04-10 17:51:45 +0200
committerHans Verkuil <hans.verkuil@cisco.com>2014-04-11 17:05:43 +0200
commit4b53f5582733c35c526ed36e108ae65a8b8d50e5 (patch)
tree7d8ca67f86f42b078360fdef3fc2a759fd70c674 /INSTALL
parent7c0567ae19ae00ba498d0d4c6c7944fc67b3b137 (diff)
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 <hegtvedt@cisco.com> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Diffstat (limited to 'INSTALL')
1 files changed, 27 insertions, 0 deletions
diff --git a/INSTALL b/INSTALL
index 6caa0f22..a26e1a09 100644
@@ -44,3 +44,30 @@ export PKG_CONFIG_LIBDIR=/path/to/cross/root/lib
./configure --host=arm-linux-gnueabihf --without-jpeg
+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
+cd /path/to/aosp
+source build/envsetup.sh
+cd /path/to/v4l-utils
+cd <utility>
+Output binary will be located in the Android out directory, below the
+target/product/<name>/system/bin/<v4l-utils executable name> path.
+The binary executable can be pushed to the target Android device using
+adb push <v4l-utils executable> /system/bin

Privacy Policy