From d01f837047b58415474fe7e842521c4d0fbef471 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Jos=C3=A9=20Fonseca?= Date: Tue, 5 Feb 2013 11:44:26 +0000 Subject: [PATCH] Update Android instructions. Not really based from personal experience, but rather on what others wrote, namely https://github.com/kanru/apitrace/commit/5948e72a25b1d2df07299db0d49f91677827478b --- INSTALL.markdown | 4 ++++ README.markdown | 14 +++++++++++--- 2 files changed, 15 insertions(+), 3 deletions(-) diff --git a/INSTALL.markdown b/INSTALL.markdown index 2228bdf..ed965b1 100644 --- a/INSTALL.markdown +++ b/INSTALL.markdown @@ -70,6 +70,10 @@ Build as: cmake -DCMAKE_TOOLCHAIN_FILE=cmake/toolchain/android.toolchain.cmake -DANDROID_API_LEVEL=9 -H. -Bbuild make -C build +You can also choose a particular ABI by passing `ANDROID_ABI` variable to +cmake, e.g., `-DANDROID_ABI=x86`. + + Windows ------- diff --git a/README.markdown b/README.markdown index 685f221..1e1d808 100644 --- a/README.markdown +++ b/README.markdown @@ -152,10 +152,9 @@ To trace the application inside gdb, invoke gdb as: ### Android ### The following instructions should work at least for Android Ice Scream -Sandwitch: +Sandwitch. -For standalone applications the instructions above for Linux should -work. To trace applications started from within the Android VM process +To trace applications started from within the Android VM process (`app_process` aka zygote) you'll have to wrap this process and enable tracing dynamically for the application to be traced. @@ -206,6 +205,15 @@ tracing dynamically for the application to be traced. Launch the application for example from the application menu. +To trace standalone applications do: + + adb push /path/to/apitrace/build/wrappers/egltrace.so /data + adb shell + # cd /data/local/tmp + # LD_PRELOAD=/data/egltrace.so test-opengl-gl2_basic + adb pull /data/local/tmp/test-opengl-gl2_basic.trace + eglretrace test-opengl-gl2_basic.trace + ### Mac OS X ### Run the application you want to trace as -- 2.43.0