Project

General

Profile

SDK » History » Version 38

dl lud, 08/21/2019 05:52 PM
Added name and links to the android-sdk package on Parabola and Trisquel.

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