Project

General

Profile

SDK » History » Version 29

Paul Kocialkowski, 01/03/2013 12:02 PM

1 1 John Smith
h1. SDK
2
3
The [[ReplicantSDK]] page holds a list of the released Replicant SDK builds.
4
5 25 Paul Kocialkowski
h2. Rationale
6 1 John Smith
7 29 Paul Kocialkowski
Replicant provides its own SDK, built from source, since the Android SDK as released by Google is distributed under a non-free license and suggests installing non-free plug-ins such as the Google APIs.
8
The Replicant SDK contains only free software and will not check for plug-ins or updates from Google.
9 1 John Smith
10 29 Paul Kocialkowski
h2. Installation
11 25 Paul Kocialkowski
12 1 John Smith
After downloading the Replicant SDK from the [[ReplicantSDK]] page, it should work the same as the Android SDK as provided by Google except that the Replicant SDK already contains a built and ready to use emulator image. 
13
Please refer to: http://developer.android.com/sdk/installing/index.html for further assistance. 
14
15 25 Paul Kocialkowski
h3. Dependencies
16
17 29 Paul Kocialkowski
h4. Required Packages
18
19
The Replicant SDK requires the following packages:
20 1 John Smith
* SDL
21 29 Paul Kocialkowski
* OpenJDK 6
22 1 John Smith
23
In some unlikely cases, creating a "JAVA_HOME" environment variable and pointing it to your JDK's true install location (not the "bin" directory but one level upward) may prove necessary.
24
25 29 Paul Kocialkowski
h5. Additional requirements for amd64
26 1 John Smith
27
Note that the Replicant SDK is built for x86 platforms and you may need compatibility libraries such as @ia32-libs@.
28 29 Paul Kocialkowski
29
h4. Command line installation
30
31
h5. Trisquel/Ubuntu/Debian
32
33
Required packages:
34
<pre>
35
apt-get install libsdl1.2debian openjdk-6-jdk
36
</pre>
37
38
Additional requirements for amd64:
39 25 Paul Kocialkowski
<pre>
40
apt-get install ia32-libs
41
</pre>
42 1 John Smith
43 25 Paul Kocialkowski
h2. Usage guides
44 2 John Smith
45 25 Paul Kocialkowski
h3. Using Eclipse
46 1 John Smith
47 25 Paul Kocialkowski
You may want to install Eclipse to work on Android Java applications. Note that this is not strictly necessary as all the required tools are already present on the SDK package. 
48 1 John Smith
49 25 Paul Kocialkowski
h4.  Installing the "Android Development Tools" plugin for Eclipse
50 1 John Smith
51 25 Paul Kocialkowski
If you have Eclipse installed and running properly, you may want to install the Android Development Tools plugin.
52 8 John Smith
53 25 Paul Kocialkowski
A solution for Eclipse 3.6 (not advised): some documentation recommends adding "https://dl-ssl.google.com/android/eclipse/" as a software update site in Eclipse, and pulling ADT from there. People have observed that this currently results in getting an ADT version which requires Eclipse 3.6, which has known issues and is not available in some widespread GNU/Linux distributions (e.g. Debian) at the moment.
54
55 1 John Smith
A somewhat manual solution:
56
57
* download ADT 0.9.8 into a stable location in your computer
58
59
http://dl.google.com/android/ADT-0.9.8.zip
60
Size: 8301417 B
61
MD5: 27e0de800512f13feae46fb554e6ee2f
62
63
* in Eclipse 3.5
64
65
- select "Window" > "Preferences" > "Install/Update" > "Available Software Sites"
66
- click the "Add" button
67
- name your software site something recognizable, e.g. "ADT 0.9.8"
68
- click "Archive" and select the "ADT-0.9.8.zip" file
69
70
* in Eclipse 3.5
71
72
- select "Help" > "Install New Software"
73
- select the "ADT 0.9.8" software site from the dropdown menu
74
- select the "Developer Tools" software package
75
- verify that the "Android DDMS" and "Android Development Tools" sub-packages were selected
76
- click the "Next" to install Android Developer Tools
77
78 2 John Smith
* restart Eclipse
79
80 25 Paul Kocialkowski
h4. Pointing "Android Development Tools" to the SDK directory
81 1 John Smith
82 9 John Smith
When you have installed ADT and restarted Eclipse, select the "Window" menu. You should see a menu entry named "Android SDK and AVD Manager". Then select "Preferences" from the "Window" menu. A menu item named "Android" should be available on the left panel.
83 3 John Smith
84 11 John Smith
If not, something is wrong. You might have the wrong flavour of Eclipse installed (the Classic, Java or RCP flavours are recommended). For example, it has been observed that the default Eclipse version which installs under Debian 6.0 ("squeeze") does not install ADT correctly, while an installation of Eclipse Classic 3.5.2 ("Galileo") downloaded from http://archive.eclipse.org/eclipse/downloads/drops/R-3.5.2-201002111343/download.php?dropFile=eclipse-SDK-3.5.2-linux-gtk.tar.gz (MD5: bde55a2354dc224cf5f26e5320e72dac) works fine. 
85 2 John Smith
86 12 John Smith
Once the "Android" menu item is available in the "Window" > "Preferences" dialog, select it. In the main panel, click the "Browse" button for the "SDK Location" field, and point it to the directory where you unzipped your Replicant SDK. Then click "Apply" or "OK".
87
88
Next time you enter this dialog, a line saying "Android 2.2.1 / Android Open Source Project / Platform: 2.2.1 / API level: 8" should be present in the list of SDK targets.
89
90 25 Paul Kocialkowski
h3. Writing a "Hello World" app in Eclipse
91 13 John Smith
92
h4. Creating an Android Virtual Device
93
94
To run your app in an emulator, you need to create an Android Virtual Device. In Eclipse, choose "Window" > "Android SDK and AVD Manager" > "Virtual Devices" > "New" and fill in the properties of the virtual device as follows:
95
96 14 John Smith
- Name: something descriptive like "AVD_for_Nexus_S"
97 13 John Smith
- Target: choose "Android 2.2.1 - API level 8" from the dropdown menu
98
- SD Card: specify the size of an emulated SD card, alternatively browse for an existing SD card image
99
- Skin: better choose "Default" and the screen resolution of your physical device, e.g. "WVGA800" for Nexus S
100
- leave other values at defaults and click "Create AVD"
101 1 John Smith
- if your disk is slow and you specified a large SD card image for creation, it may take a few seconds to complete
102 14 John Smith
103 17 John Smith
h4. Creating a project
104 14 John Smith
105
In Eclipse, choose "File" > "New" > "Project". In the tree of possible project types, a branch named "Android" should exist. Open it, select the project type "Android Project" and click "Next".
106 15 John Smith
107
Enter a name for your project, e.g. "hello". For "Content", select "Create new project in workspace" and "use default location". The project will be created in your local Eclipse workspace directory, in a subdirectory corresponding to the project name.
108
109 16 John Smith
Besides the project name, enter a friendly name for your application, e.g. "Hello World". Enter its package name, which can be either public (e.g. "com.example.hello") or private (e.g. "hello.test"). If you want the first piece of your application's user interface to be auto-created, leave the "Create Activity" checkbox checked and enter someting like "MainActivity" for the name of the "Activity" class to create.
110 15 John Smith
111 1 John Smith
Leave the minimum SDK version blank. Finally click "Finish" and your project should appear in Eclipse's left-hand projects tree.
112 17 John Smith
113
h4. Adding some code and resources into a project
114
115
To have your application's MainActivity class do something, consider adding some code. For example, you might want your application to have a button which closes it. In this sample, we specify the design of user interface elements in a separate XML resource file, so don't be surprised when you don't see anything related to their design here:
116
117
<pre>package hello.test;
118
119
import android.app.Activity;
120
import android.os.Bundle;
121
import android.view.View;
122
import android.widget.Button;
123
124
public class MainActivity extends Activity {
125
126
    @Override
127
    public void onCreate(Bundle savedInstanceState) {
128
    	
129
        super.onCreate(savedInstanceState);
130
        setContentView(R.layout.main);
131
        
132
        Button buttonFinish = (Button) findViewById(R.id.buttonFinish);
133
        buttonFinish.setOnClickListener(new View.OnClickListener() {
134
			@Override
135
			public void onClick(View v) {
136
				finish();
137
			}
138
		});
139
    }
140
}</pre>
141
142
You may notice how the constructor of MainActivity calls "setContentView(R.layout.main)". In this statement, R is a special resource class, pointing to resources hosted in the "res" directory of your project. The "layout" class limits the choice to layout resources hosted under the "res/layout" while "main" is the name of a layout resource file "main.xml" located there.
143
144
We need to create this resource file now. I would recommend having it be like this:
145
146
<pre><?xml version="1.0" encoding="utf-8"?>
147
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
148
    android:orientation="vertical"
149
    android:layout_width="fill_parent"
150
    android:layout_height="fill_parent"
151
    >
152
<TextView
153
    android:id="@+id/textInfo"
154
    android:layout_width="fill_parent" 
155
    android:layout_height="wrap_content" 
156
    android:text="Click button to close app."
157
    />
158
<Button android:id="@+id/buttonFinish"
159
    android:layout_width="wrap_content"
160
    android:layout_height="wrap_content"
161 18 John Smith
    android:text="Close" />
162 17 John Smith
</LinearLayout>
163 1 John Smith
</pre>
164 18 John Smith
165 19 John Smith
Together, it makes sense. The "LinearLayout" element directs the application to fill the screen with its window ("fill_parent" for width and height). The "TextView" element displays a text field expanding to cover window width, but limits itself to content height ("wrap_content"). The "Button" element is a button named "buttonFinish", big enough to accommodate its content. Code obtains a handle to it by calling "Button buttonFinish = (Button) findViewById(R.id.buttonFinish);"), and creates an event listener for its OnClick event. This event listener calls "finish()" to close the app.
166 20 John Smith
167
h4. Running the app on an Android Virtual Device
168
169
Once you've coded your app, choose "Run" > "Run" in Eclipse. A dialog named "Android Device Chooser" will open, asking you to choose a device for it. Select the "Launch a new Android Virtual Device" checkbox and the virtual device you previously made, should become available for selection (select it and click "OK"). The virtual device will start booting up and will eventually run your app. Beware, on slow computers (e.g. an old model of Asus EEE PC) this can take minutes.
170 21 John Smith
171
h4. Running the app on a real Replicant device
172
173 22 John Smith
1. Declare your app as debuggable. In the left-hand sidebar of Eclipse, your project's resource tree should contain a file resource named "AndroidManifest.xml". Right-click it and choose "Open With". Proceed by choosing either "Android Manifest Editor" or "Text Editor". If you preferred the manifest editor GUI, select the tab "Application" at its bottom. On the "Application" tab, set the field "Debuggable" to "true". If you preferred the text editor, append the property "android:debuggable="true" to the "<application>" element.
174
175
2. Enable USB debugging on your device, for example by choosing "Menu" > "Settings" > "Applications" > "Development" and checking the "USB Debugging" checkbox.
176 23 John Smith
177
3. Verify that your device is visible. Prior to this, on Windows, you should install the ADB USB driver. On Mac, you should not need to configure anything. On some Linuxes (e.g. Ubuntu), you might need to add uDev rules (consult the "docs/guide/developing/device.html" file in your SDK directory, it contains detailed instructions).
178
179 24 John Smith
Do the verification by issuing "adb devices" on command line. Make your your ADB (Android Debug Bridge) is included in your PATH variable. If it lists your device and its numeric ID, all should be fine. If it lists "?????????" for the ID and says "No permissions" under Linux, you might need to restart the ADB server (become root and issue: "adb kill-server; adb start-server", this presumes that ADB is also present in the root user's PATH).
180 23 John Smith
181 24 John Smith
4. Run the app. Without a customized run configuration, Eclipse should display the "Android Device Chooser" dialog, letting you choose. 
182 23 John Smith
183
5. Optionally, configure automatic deployment: if you want to automatically deploy to devices when they're attached, create a run configuration for your app, proceeding to select "Deployment Target Selection Mode: Automatic" in the "Target" tab.