Project

General

Profile

SDK » History » Version 32

Paul Kocialkowski, 09/28/2014 12:43 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 31 Paul Kocialkowski
* Ant
23 1 John Smith
24
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.
25
26 29 Paul Kocialkowski
h5. Additional requirements for amd64
27 1 John Smith
28
Note that the Replicant SDK is built for x86 platforms and you may need compatibility libraries such as @ia32-libs@.
29 29 Paul Kocialkowski
30
h4. Command line installation
31
32
h5. Trisquel/Ubuntu/Debian
33
34
Required packages:
35 1 John Smith
<pre>
36 31 Paul Kocialkowski
apt-get install libsdl1.2debian openjdk-6-jdk ant
37 29 Paul Kocialkowski
</pre>
38
39
Additional requirements for amd64:
40 25 Paul Kocialkowski
<pre>
41
apt-get install ia32-libs
42
</pre>
43 1 John Smith
44 25 Paul Kocialkowski
h2. Usage guides
45 2 John Smith
46 25 Paul Kocialkowski
h3. Using Eclipse
47 1 John Smith
48 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. 
49 1 John Smith
50 25 Paul Kocialkowski
h4.  Installing the "Android Development Tools" plugin for Eclipse
51 1 John Smith
52 30 James Adams
The following instructions work with Eclipse 3.7.2 (Indigo) as installed via Apt under Trisquel Toutatis GNU/Linux.
53
<pre>
54
sudo aptitude install eclipse
55
</pre>
56 1 John Smith
57 30 James Adams
Once you have Eclipse installed and running properly, you may want to install the Android Development Tools plugin.
58 1 John Smith
59 32 Paul Kocialkowski
* The Replicant 4.0 SDK requires ADT version 16 while the Replicant 4.2 SDK requires ADT version 20. You will need to download it from Google's archives and then manually install it in Eclipse:
60 1 John Smith
61
http://dl.google.com/android/ADT-16.0.0.zip
62 32 Paul Kocialkowski
http://dl.google.com/android/ADT-20.0.0.zip
63 1 John Smith
64 30 James Adams
* in Eclipse 3.7
65 1 John Smith
66
- select "Window" > "Preferences" > "Install/Update" > "Available Software Sites"
67
- click the "Add" button
68 32 Paul Kocialkowski
- name your software site something recognizable, e.g. "ADT"
69
- click "Archive" and select the ADT zip file
70 1 John Smith
71 30 James Adams
* in Eclipse 3.7
72 1 John Smith
73
- select "Help" > "Install New Software"
74 32 Paul Kocialkowski
- select the "ADT"/ software site from the dropdown menu
75 1 John Smith
- select the "Developer Tools" software package
76 2 John Smith
- verify that the "Android DDMS" and "Android Development Tools" sub-packages were selected
77
- click the "Next" to install Android Developer Tools
78 25 Paul Kocialkowski
79 1 John Smith
* restart Eclipse
80
81 9 John Smith
h4. Pointing "Android Development Tools" to the SDK directory
82 11 John Smith
83 2 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.
84 12 John Smith
85 32 Paul Kocialkowski
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 4.0 SDK. Then click "Apply" or "OK".
86 12 John Smith
87 30 James Adams
Next time you enter this dialog, a line saying "Android 4.0.3 / Android Open Source Project / Platform: 4.0.3 / API level: 15" should be present in the list of SDK targets.
88 25 Paul Kocialkowski
89 13 John Smith
h3. Writing a "Hello World" app in Eclipse
90
91
h4. Creating an Android Virtual Device
92
93
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:
94 14 John Smith
95 13 John Smith
- Name: something descriptive like "AVD_for_Nexus_S"
96 30 James Adams
- Target: choose "Android 4.0.3 - API level 15" from the dropdown menu
97 13 John Smith
- SD Card: specify the size of an emulated SD card, alternatively browse for an existing SD card image
98
- Skin: better choose "Default" and the screen resolution of your physical device, e.g. "WVGA800" for Nexus S
99 1 John Smith
- leave other values at defaults and click "Create AVD"
100 14 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
101 17 John Smith
102 14 John Smith
h4. Creating a project
103
104 15 John Smith
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".
105
106
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.
107 16 John Smith
108 15 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.
109 1 John Smith
110 17 John Smith
Leave the minimum SDK version blank. Finally click "Finish" and your project should appear in Eclipse's left-hand projects tree.
111
112
h4. Adding some code and resources into a project
113
114
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:
115
116
<pre>package hello.test;
117
118
import android.app.Activity;
119
import android.os.Bundle;
120
import android.view.View;
121
import android.widget.Button;
122
123
public class MainActivity extends Activity {
124
125
    @Override
126
    public void onCreate(Bundle savedInstanceState) {
127
    	
128
        super.onCreate(savedInstanceState);
129
        setContentView(R.layout.main);
130
        
131
        Button buttonFinish = (Button) findViewById(R.id.buttonFinish);
132
        buttonFinish.setOnClickListener(new View.OnClickListener() {
133
			@Override
134
			public void onClick(View v) {
135
				finish();
136
			}
137
		});
138
    }
139
}</pre>
140
141
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.
142
143
We need to create this resource file now. I would recommend having it be like this:
144
145
<pre><?xml version="1.0" encoding="utf-8"?>
146
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
147
    android:orientation="vertical"
148
    android:layout_width="fill_parent"
149
    android:layout_height="fill_parent"
150
    >
151
<TextView
152
    android:id="@+id/textInfo"
153
    android:layout_width="fill_parent" 
154
    android:layout_height="wrap_content" 
155
    android:text="Click button to close app."
156
    />
157
<Button android:id="@+id/buttonFinish"
158
    android:layout_width="wrap_content"
159 18 John Smith
    android:layout_height="wrap_content"
160 17 John Smith
    android:text="Close" />
161 1 John Smith
</LinearLayout>
162 18 John Smith
</pre>
163 19 John Smith
164 20 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.
165
166
h4. Running the app on an Android Virtual Device
167
168 21 John Smith
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.
169
170
h4. Running the app on a real Replicant device
171 22 John Smith
172
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.
173
174 23 John Smith
2. Enable USB debugging on your device, for example by choosing "Menu" > "Settings" > "Applications" > "Development" and checking the "USB Debugging" checkbox.
175
176
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).
177 24 John Smith
178 23 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).
179 24 John Smith
180 23 John Smith
4. Run the app. Without a customized run configuration, Eclipse should display the "Android Device Chooser" dialog, letting you choose. 
181
182 1 John Smith
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.