generic-library/webrtc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

AppRTCDemo(android): README updates for a shrinking envsetup.sh world.

Browse Source 
There was duplicated (and out of date!) information in README relative to
getting-started so de-duped to point to getting-started as the canonical
reference.

R=wu@webrtc.org

Review URL: https://webrtc-codereview.appspot.com/15589006

git-svn-id: http://webrtc.googlecode.com/svn/trunk@6265 4adac7df-926f-26a2-2b94-8c16560cd09d
This commit is contained in:
fischman@webrtc.org 2014-05-28 17:29:09 +00:00
parent b364016cbb
commit 43a1395370
1 changed files with 1 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
talk/examples/android/README
View File

@ -1,19 +1,9 @@
This directory contains an example Android client for http://apprtc.appspot.com
Prerequisites:
- Make sure gclient is checking out tools necessary to target Android: your
.gclient file should contain a line like:
target_os = ['android', 'unix']
Make sure to re-run gclient sync after adding this to download the tools.
- Env vars need to be set up to target Android; easiest way to do this is to run
(from the libjingle trunk directory):
. ./build/android/envsetup.sh
Note that this clobbers any previously-set $GYP_DEFINES so it must be done
before the next item.
- "Android Specific Steps" on http://www.webrtc.org/reference/getting-started
- Set up webrtc-related GYP variables:
export GYP_DEFINES="build_with_libjingle=1 build_with_chromium=0 libjingle_java=1 $GYP_DEFINES"
export JAVA_HOME=</path/to/JDK>
export PATH=$JAVA_HOME/bin:$PATH
To cause WEBRTC_LOGGING to emit to Android's logcat, add enable_tracing=1 to
the $GYP_DEFINES above.
- When targeting both desktop & android, make sure to use a different output_dir