blob: 7d57a6e3e11c02dc9101ab96b090200672d293ee (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
Compiling
=========
Preconditions
----------------
1. Android SDK installed (follow instructions from http://developer.android.com/sdk/index.html)
2. API version 16 or version installed.
2. Ant 1.6 or greater
Instructions to compile
-----------------------
1. cd $PROJECT_LOCATION/leap_android
2. ./compile.sh
Postconditions
--------------
1. $PROJECT_LOCATION/leap_android/bin/LEAP Android-debug.apk exists
Running on the emulator
=========================
Preconditions
-----------------
1. Android SDK is installed, and its tools are in the PATH.
2. leap_android has been compiled.
3. An avd exists in ~/.android/avd/ (if you do not have one, follow instructions from http://developer.android.com/tools/devices/managing-avds-cmdline.html)
Instructions to run on the emulator
-----------------------------------
1. cd $PROJECT_LOCATION/leap_android
1. Run script: ./run.sh @AVD-NAME . (avd names are the names of the files in ~/.android/avd with extension .avd).
Postconditions
--------------
1. LEAP Android is running.
Debugging from console
======================
Preconditions
-----------------
1. Android SDK is installed, and its tools are in the PATH.
2. leap_android has been compiled.
3. An avd exists in ~/.android/avd/ (if you do not have one, follow instructions from http://developer.android.com/tools/devices/managing-avds-cmdline.html).
4. jdb is installed (this program is part of OpenJDK 7)
Instructions to debug from the console
-----------------------------------
1. cd $PROJECT_LOCATION/leap_android
2. Run script: ./debug.sh @AVD-NAME . (avd names are the names of the files in ~/.android/avd with extension .avd).
Postconditions
--------------
1. LEAP Android is running.
2. LEAP Android does not show the message "Application LEAP for Android (process se.leap.leapclient) is waiting for the debugger to attach".
3. You are in a jdb debuggin session.
|
