Project

General

Profile

SDK » History » Version 48

Denis 'GNUtoo' Carikli, 08/22/2021 12:04 AM
add distro releases code names

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