| commit | 9a1cbd471fb0a21443a44817ebfc794fb12b2484 | [log] [tgz] |
|---|---|---|
| author | Tom Turney <tturney@google.com> | Mon May 15 21:40:13 2017 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Mon May 15 21:40:13 2017 +0000 |
| tree | c2274537803feb7afee2a7e0c7c120eee8b32e57 | |
| parent | 2e9e36833d2ca737171aa803cf26efbe644cf968 [diff] | |
| parent | a3883d51ad354260d556769f355a107c956a41a5 [diff] |
Merge "Expose new GATT Client/Server APIs through facades (1/2)" into oc-dev am: 0e4aa6c1a9 -s ours am: a3883d51ad Change-Id: I7b4b4e586e1ee1e96f519f9a53acf3d4d80aeae7
Originally authored by Damon Kohler, Scripting Layer for Android, SL4A, is an automation toolset for calling Android APIs in a platform-independent manner. It supports both remote automation via ADB as well as execution of scripts from on-device via a series of lightweight translation layers.
Due to its inclusion in AOSP as a privileged app, building SL4A requires a system build.
For the initial build of Android:
cd <ANDROID_SOURCE_ROOT> source build/envsetup.sh lunch aosp_<TARGET> make [-j15]
where <ANDROID_SOURCE_ROOT> is the root directory of the android tree and <TARGET> is the lunch target name
Then Build SL4A:
cd <ANDROID_SOURCE_ROOT>/external/sl4a mm [-j15]
If you are not using a custom buildspec, create one as follows:
cp <ANDROID_SOURCE_ROOT>/build/buildspec.mk.default <ANDROID_SOURCE_ROOT>/buildspec.mk
Modify the buildspec to build SL4A as a custom module by editing the line '#CUSTOM_MODULES:=' to 'CUSTOM_MODULES:=sl4a':
sed -i 's/#CUSTOM_MODULES:=/CUSTOM_MODULES:=sl4a/' <ANDROID_SOURCE_ROOT>/buildspec.mk
Run the following command:
adb install -r <ANDROID_SOURCE_ROOT>/out/target/product/<TARGET>/data/app/sl4a/sl4a.apk
a) SL4A may be launched from Android as a normal App; or
b) To enable RPC access from the command prompt:
adb forward tcp:<HOST_PORT_NUM> tcp:<DEVICE_PORT_NUM>
adb shell "am start -a com.googlecode.android_scripting.action.LAUNCH_SERVER \
--ei com.googlecode.android_scripting.extra.USE_SERVICE_PORT <DEVICE_PORT_NUM> \
com.googlecode.android_scripting/.activity.ScriptingLayerServiceLauncher"
where <HOST_PORT_NUM> and <DEVICE_PORT_NUM> are the tcp ports on the host computer and device.
From SL4A source directory run this command:
python Docs/generate_api_reference_md.py
In the Docs directory there should now be an ApiReference.md file that contains which RPC functions are available in SL4A as well as documentation for the RPC functions.