Custom Drawn Interface/Android/ja: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		Go back to [[Custom Drawn Interface]]\
2		-	\
	2	+
3	3		※今のところ、Windows上でAndroidプログラミングを実際にできるようにすることを優先目標として記述しています。そのため、原文の翻訳となっていないところが多いです。間違い等はどんどん修正していただけると幸いです。(2014-01-26 by malcome)\
4		-	\
5	4
6	5		## Architecture
7	6
8	7		LCL-CustomDrawn-Android utilizes a minimal Java application which communicates with our Pascal library and sends all events to it and also obeys commands from it. The communication is done via JNI as supported by Google. The controls are not native, instead they are all drawing using TRawImage+TLazIntfImage+TLazCanvas and events and the painting are clipped using LazRegions. The drawing itself is done in Pascal using jnigraphics to draw on a Bitmap Java object which is then drawn by the minimal Java activity on a SurfaceView.
9	8
10	9		Our previous and short-lived attempt to write an LCL Interface for Android (LCL-Android) utilized a non-standard method of using native executables which communicated with a Java machine via Pipes. This method was abandoned because it was considered unsupported by Google. It is considered obsolete and people should use LCL-CustomDrawn-Android instead. This older interface was documented in [[Android Interface]].
11	10
12	11		## Roadmap
13	12
14	13		Part 1, until March 2012:
15	14
16		-	~~1. <s>Build the set of [[Lazarus Custom Drawn Controls]]</s>~~
17		-	~~2. <s>Initial bindings for the Android APIs</s>~~
18		-	~~3. <s>Create an application to automatically generate the bindings</s>~~
19		-	~~4. <s>Start the new widgetset</s>~~
20		-	~~5. <s>Implement support for JNI</s>~~
21		-	~~6. <s>Merge the Lazarus Custom Drawn Controls into the LCL and use them to implement all basic controls</s>~~
22		-	~~7. <s>Add text support for Android</s>~~
23		-	~~8. <s>Implement basic window client area scrolling</s>~~
	15	+	1. Build the set of [[Lazarus Custom Drawn Controls]]
	16	+	2. Initial bindings for the Android APIs
	17	+	3. Create an application to automatically generate the bindings
	18	+	4. Start the new widgetset
	19	+	5. Implement support for JNI
	20	+	6. Merge the Lazarus Custom Drawn Controls into the LCL and use them to implement all basic controls
	21	+	7. Add text support for Android
	22	+	8. Implement basic window client area scrolling
24	23		9. Add mobile emulator for desktop platforms
25	24		10. Improve the mobile scrolling
26		-	~~11. <s>Add text support in X11</s>~~
27		-	~~12. <s>Add DPI awareness and adaptation in the LCL</s>~~
28		-	~~13. <s>Add non-native text support via pasfreetype</s>~~
	25	+	11. Add text support in X11
	26	+	12. Add DPI awareness and adaptation in the LCL
	27	+	13. Add non-native text support via pasfreetype
29	28
30	29		Part 2: April, May, June 2012:
31	30
32		-	~~1. <s>TButton improve the Android visual</s>~~
	31	+	1. TButton improve the Android visual
33	32		2. TBitBtn
34		-	~~3. <s>TRadioButton finish the native look</s>~~
	33	+	3. TRadioButton finish the native look
35	34		4. Calendar dialog -\> Problematic as the LCL has no calendar dialog, it just opens a normal form and puts a calendar on it, so we need a TCDCalendar widget
36	35		5. MaskEdit
37		-	~~6. <s>Improve TComboBox</s>~~
	36	+	6. Improve TComboBox
38	37		7. TMemo
39	38		8. TListView as a list with columns
40		-	~~9. <s>TMainMenu</s>~~
	39	+	9. TMainMenu
41	40		10. Database with sqlite
42	41		11. Barcode reading
43	42		12. Windows add-on installer
44	43
45	44		## Using the Android SDK, Emulator and Phones
46	45
47	46		[[Custom Drawn Interface/Using the Android SDK, Emulator and Phones]]
48	47
49	48		## Android Programming
50	49
51	50		See [[Android Programming]], also includes caracteristics of the various phones relevant for programming.
52	51
53	52		## Configuring the Free Pascal Compiler for Android
54	53
55	54		### Use the ready Virtual Box Image with FPC and Lazarus
56	55
57	56		The fastest way to configure Free Pascal and Lazarus for Android development is simply using a pre-configured virtual machine image which already includes Mageia Linux 1, KDE, Lazarus 0.9.31, Subversion, Free Pascal for both x86-linux and arm-linux (targetting Android), the Android SDK, the Android NDK, Java, Ant, Gtk2 and all it's development packages, the GNU debugger (GDB), subversion and everything else necessary for building Android applications with Lazarus.
58	57
59	58		The download like for the virtual machine image is: <https://sourceforge.net/projects/p-tools/files/Lazarus_for_Android_VM_Image/snapshot_30_dez_2011/> (warning: the VirtualBox image was created using the Mac OS X default Zip utility and not all zip applications can handle it. The Mac OS X default zip application can, and [PeaZip](https://peazip.github.io/) too and [WinRAR](http://win-rar.com/download.html) too. Both 7-Zip and the Windows 7 default unzipper fail.
60	59
61	60		The virtual machine image is composed by two files: “Android Devel VM.vbox” and “Android Devel VM.hdd”. Both need to be located in the same folder and also note that the source forge download is a zipped file, so it needs to be unzipped. After unzipping the VM image has 5,2GB. To use this virtual machine one should install Virtual Box and then use it to open the .vbox file. Then one can already use this Linux virtual machine to build Android applications. The process of building an application involves first opening Lazarus and building the application in Lazarus, for example the example project available on ~/Programas/lazarus/example/androidlcl/ and then going into the Linux terminal, navigating to ~/Programas/lazarus/example/androidlcl/android and issuing the command “ant debug” which will generate the APK file in ~/Programas/ lazarus/example/androidlcl/android/bin/LCLExample-debug.apk. There are two users in the virtual machine: “root” and “pascaldev” and both of them use the password “root”.
62	61
63	62		Note that the virtual machine contains the Lazarus source code from when it was created, but one can also use svn update to get the latest code. Note that this involves some risks, however, as the trunk version might ocasionally contain problems.
64	63
65	64		### Windows 上で Lazarus を用いて Android アプリを開発するための準備
66	65
67	66		Step 1 - Android SDK の準備
68	67
69	68		<http://developer.android.com/sdk/index.html> から Windows 用 Android SDK の zip ファイルをダウンロードし、適当なフォルダ（以下ではc:\work\android\sdkと仮定）に解凍します。\
70	69		2015-12-07追記: 上記ウェブサイトの、「Other Download Options」「SDK Tools Only」セクションにある、android-sdk_r24.4.1-windows.zip で動作することを確認しました。\
71		-	\
72		-	\
	70	+
73	71		Step 2 - Android NDK の準備
74	72
75	73		<http://developer.android.com/ndk/downloads/index.html> から Windows 用 Android NDK をダウンロードし、適当なフォルダ（以下ではc:\work\android\ndkと仮定）に解凍します。\
76	74		2015-12-07追記: android-ndk-r10e-windows-x86.exe にて動作確認しました。\
77		-	\
	75	+
78	76		Step 3 - Android JDK の準備
79	77
80	78		作成予定のプログラムで JAVAのライブラリを使用しない場合でも、apk ファイルの作成のために JDK に含まれるツールを使用します。したがって、JDK をインストールする必要があります。\
81	79		<http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html> から　Windows 用 JDK の exe ファイルをダウンロードしてインストールしてください。(以下ではC:\Program Files\Java\jdk1.7.0_51 にインストールしたと仮定します）\
82	80		2014-01-25 動作確認: jdk-7u51-windows-i586.exe\
83		-	\
	81	+
84	82		Step 4 - Apatch Ant の準備
85	83
86	84		原文では Windows で Apatch Ant を使用せずに apk ファイルを作成できることを紹介していますが、Apatch Ant を使用した方が楽ですしネット上の情報も多いです。\
87	85		<http://ant.apache.org/bindownload.cgi> から Apache Ant をダウンロードし(2015-12-03追記:apache-ant-1.9.6-bin.zipで動作確認しました）、適当なフォルダ（以下ではc:\work\tools\antと仮定）に展開してください。\
88	86		Apatch Ant による apk ファイルの作成方法：\
89	87		アプリケーション固有の build.xml があるフォルダ内に次のような buildapk.bat を作成して、コマンドプロンプトから「buildapk debug」などとしてバッチを実行することで apk ファイルが作成できます。
90	88
91	89		REM Adjust the path to yours path
92	90		set ANT_HOME=C:\work\tools\ant
93	91		set JAVA_HOME=C:\Program Files\Java\jdk1.7.0_51
94	92
95	93		set Path=%JAVA_HOME%\bin
96	94
97	95		%ANT_HOME%\bin\ant %1 %2 %3 %4 %5 %6 %7 %8 %9
98	96
99		-	\
100		-	\
101	97		Step 5 - Lazarus の準備
102	98
103	99		通常は最新の安定版をダウンロードしてインストールすれば十分です。(以下では、c:\lazarus にインストールされたものと仮定する)\
104		-	\
	100	+
105	101		Step 6 - FPC 3.0.0 の準備
106	102
107	103		<ftp://wiki.freepascal.org/pub/fpc/dist/3.0.0/source/> から、fpc-3.0.0.source.zip をダウンロードして適当なフォルダ(以下では c:\work\fpcsrc と仮定)に展開します。\
108	104		次に、c:\work\fpcsrc\buildfpc.bat を次の内容で作成します。\
109	105		各PATH は環境に合わせて設定しなおしてください。なお、ここでは ARMv6 を最低現の対象機種としています。また、FPCのバージョン部分は適切に修正してください。下記ではLazarus 1.4.4 に付属しているFPC2.6.4を使用してFPC3.0.0をビルドしています。なお、Lazarus にすでに FPC 3.0.0 をインストール済みの場合は、クロスコンパイラだけビルドすればよいので、バッチ内の「Build FPC」、「Create fpc.cfg」という部分は不要です。
110	106
111	107		REM Adjust the path to yours path
112	108		SET LAZ_PATH=C:\lazarus
113	109		SET NDK_PATH=C:\work\android\ndk\toolchains\arm-linux-androideabi-4.8\prebuilt\windows\bin
114	110
115	111		Set Path=%NDK_PATH%;%LAZ_PATH%\fpc\2.6.4\bin\i386-win32
116	112
117	113		REM =============== Build FPC
118	114		make all
119	115		make install INSTALL_PREFIX=%LAZ_PATH%\fpc\3.0.0
120	116
121	117		REM =============== Build cross compiler
122	118		make clean crossall crossinstall OS_TARGET=android CPU_TARGET=arm CROSSOPT="-OoFASTMATH -CpARMV6" INSTALL_PREFIX=%LAZ_PATH%\fpc\3.0.0
123	119
124	120		REM =============== Create fpc.cfg
125	121		%LAZ_PATH%\fpc\3.0.0\bin\i386-win32\fpcmkcfg.exe -d basepath=%LAZ_PATH%\fpc\3.0.0 -o %LAZ_PATH%\fpc\3.0.0\bin\i386-win32\fpc.cfg
126	122
127	123		次に、コマンドプロンプトを起動し、下記のコマンドを入力します。
128	124
129	125		cd c:\work\fpcsrc
130	126		bildfpc
131	127
132	128		これで FPC の準備ができました。\
133		-	\
134		-	\
	129	+
135	130		Step 7 - cross-binutils のコピー
136	131
137	132		C:\work\Android\ndk\toolchains\arm-linux-androideabi-4.8\prebuilt\windows\bin　フォルダ内のすべてのファイル（おそらくすべて arm-linux-androideabi-*.exe という名前)を、C:\lazarus\fpc\3.0.0\bin\i386-win32 フォルダにコピーします。\
138		-	\
	133	+
139	134		Step 8 - Lazarus の設定
140	135
141	136		Lazarus を起動し、Tools-\>Options の、Environment-\>Files の、Compiler executable の 2.6.4 という部分を 3.0.0 に変更します。\
142	137		例）　「C:\lazarus\fpc\2.6.4\bin\i386-win32\fpc.exe」を、「C:\lazarus\fpc\3.0.0\bin\i386-win32\fpc.exe」に変更。\
143		-	\
144		-	\
	138	+
145	139		・・・この後は、新規プロジェクトでLinuxライブラリ(.so)を作成し各種設定をしますが、Android プログラミングの知識がやや必要になります。・・・\
146		-	\
	140	+
147	141		Project-\>Project Options の、Compiler Options-\>Paths の、Libraries に\
148	142		C:\work\Android\ndk\platforms\android-9\arch-arm\usr\lib\\\
149	143		を追加する。(andoroid-9 の数字の部分は minimum API レベルにより変わる)\
150		-	\
	144	+
151	145		Project-\>Project Options の、Compiler Options-\>Other の、Custom options に\
152	146		-OoFASTMATH\
153	147		などを追加する。なお、古いサンプルソースなんかですと「-dANDROID」というオプションが追加されていることがありますが現在は不要のようです。\
154		-	\
	148	+
155	149		Project-\>Project Options の、Compiler Options-\>Config and Target の、 Target OS を Android に、Taget CPU を arm に、Target processor を ARMV6などに設定する。\
156		-	\
	150	+
157	151		さらに、Android SDK に付属する SDK Manager.exe を用いて、使用するAPI（例：Android 2.3.3(API10)）を導入するなどの作業も必要です。\
158		-	\
	152	+
159	153		・・・ここまですれば [[Android Programming/ja\|Android_Programming]] で紹介されている NDK_OpenGL_example はコンパイルできましたし、完成した apk を実機にインストールして見事に動作させることができました。しかし、今のところ、下記の androidlcltest.lpi は、「・・・fpc\2.7.1\bin\i386-win32\arm-linux-androideabi-ld.bfd.exe: BFD (GNU Binutils) 2.23.2 assertion fail /s/ndk-toolchain/src/build/../binutils/binutils-2.23/bfd/elf32-arm.c:12336」というエラーが出てコンパイルできませんでした。個人的には NDK で OpenGL が使えれば十分なので、Custom Drawn についての調査は時間がかかるかもしれません。識者の情報をお待ちします。\
160		-	\
	154	+
161	155		Now you can already build the example project androidlcltest.lpi using the Windows-Release build mode
162	156
163	157		### Building the compiler yourself in Linux
164	158
165	159		See [[Setup Cross Compile For ARM]] and make sure to use the option OPT="-dFPC_ARMEL" for building the compiler.
166	160
167	161		### Using the pre-compiled compiler in Linux
168	162
169	163		A pre-compiled compiler is provided for convenience for users. The following steps were tested in Mandriva Linux 2010.0 and 2010.1:
170	164
171	165		Required Environment
172	166
173	167		- The latest stable FPC installed in the system via the RPM / DEB / TAR package
174	168
175	169		Step 1 - Install the cross-binutils
176	170
177	171		For Mandriva Linux the RPM package containing arm-linux-as, arm-linux-ld, etc, which are the cross-binutils can be found here: <http://rpm.pbone.net/index.php3/stat/4/idpl/14252825/dir/mandriva_2010/com/cross-arm-binutils-2.20.51.0.4-2mnb2.i586.rpm.html>
178	172
179	173		Just download the RPM package and install it using:
180	174
181	175		`rpm -ivh cross-arm-binutils-2.20.51.0.4-2mnb2.i586.rpm `
182	176
183	177		In Mandriva Linux 2010.0 the dependencies won't match, as the package is for 2010.1, but one can simply ignore this problem and it works fine using --nodeps:
184	178
185	179		`rpm -ivh --nodeps cross-arm-binutils-2.20.51.0.4-2mnb2.i586.rpm `
186	180
187	181		For other distributions use the corresponding package, or else read the instructions for building the cross-binutils yourself at [[Setup Cross Compile For ARM]]
188	182
189	183		Step 2 - Configure the cross-binutils
190	184
191	185		The assembler needs a parameter to tell it which ARM ABI to use. A choice which works good is EABI-5, which is compatible with all Android devices available as of Jan 2011. To set this, we will rename the original assembler and substitute it with a shell script which passes the desired parameter. These commands will do it:
192	186
193	187		`su`\
194	188		`mv /usr/bin/arm-linux-as /usr/bin/arm-linux-as_org`\
195	189		`gedit /usr/bin/arm-linux-as`
196	190
197	191		Now paste into the editor this code:
198	192
199	193		`#!/bin/sh`\
200	194		`/usr/bin/arm-linux-as_org -meabi=5 $@`
201	195
202	196		And don't forget to then make it executable:
203	197
204	198		`chmod 755 /usr/bin/arm-linux-as`
205	199
206	200		Step 3 - Install the Free Pascal Cross-Compiler
207	201
208	202		At this point the pre-compiled FPC can be download from here: <http://sourceforge.net/projects/p-tools/files/Free%20Pascal%20for%20ARM/>
209	203
210	204		Then use these commands to install the pre-compiled Free Pascal cross-compiler into /usr:
211	205
212	206		`[felipe@localhost Programas]$ ls -l`\
213	207		`total 20664`\
214	208		`-rw-rw-r-- 1 felipe felipe 17098552 2010-10-25 08:17 fpc-2.5.1.arm-linux.tar.gz`\
215	209		`[felipe@localhost Programas]$ su`\
216	210		`Password: `\
217	211		`[root@localhost Programas]# cp fpc-2.5.1.arm-linux.tar.gz /usr/`\
218	212		`[root@localhost Programas]# cd /usr/`\
219	213		`[root@localhost usr]# tar -xvf fpc-2.5.1.arm-linux.tar.gz `\
220	214		`[root@localhost usr]# ln -s /usr/lib/fpc/2.5.1/ppcrossarm /usr/bin/ppcrossarm`
221	215
222	216		Step 4 - Verify if your Cross-Compiler works
223	217
224	218		If you made no errors in the previous steps, it should work, so try to call it like this:
225	219
226	220		`[felipe@localhost Programas]$ /usr/bin/ppcrossarm`
227	221
228	222		If this command works and fpc shows its options, then you configured the cross-compiler correctly, if not, then try to find out if your symbolic link points to a correct location with this command:
229	223
230	224		\[felipe@localhost Programas\]\$ ls -ls /usr/bin/ppc*
231	225
232	226		Now we are ready to compile Android applications using the Lazarus IDE! Configuring the fpc.cfg file isn't necessary, the old compiler will automatically find the new compiler and it's object files.
233	227
234	228		## Compiling the example LCL Android Application
235	229
236	230		Step 1 - Download the source code
237	231
238	232		The source code of the example is located inside the Lazarus sources in lazarus/examples/androidlcl/androidlcltest.lpi
239	233
240	234		Step 2 - Make sure you have the Java JDK and the Android SDK and NDK installed
241	235
242	236		Read here: [[Custom Drawn Interface/Android\|Custom_Drawn_Interface/Android#Install_the_Java_JDK_and_the_Android_SDK_and_NDK]]
243	237
244	238		Step 3 - Build the project using the Lazarus IDE
245	239
246	240		Configuring Lazarus itself to use the new compiler should not normally be necessary because fpc should be able to find the symlink created, but if you have trouble in this part you can try to hard code the compiler path to use the new crosscompiler. To hardcode the compiler path in cause of trouble go to the menu "Tools-\>Options" and change the "Compiler Path" to "/usr/bin/ppcrossarm"
247	241
248	242		But it is necessary to configure the LPI file to build the example. Open the Project Options dialog of the androidlcltest.lpi project and go to the section Paths and change the libraries path to reflect the correct paths of where your Android NDK was installed and where your jnigraphics.so, libc.so, etc, libraries are located for your target Android API level. For LCL-CustomDrawn-Android API level 8 is the best choice, because it supports Android 2.2+ like the LCL. The image below shows where to configure this:
249	243
250		-	~~<figure>~~
251		-	~~<img src="Configure_androidlcl_libraries.jpg" title="Configure_androidlcl_libraries.jpg" />~~
252		-	~~<figcaption>Configure_androidlcl_libraries.jpg</figcaption>~~
253		-	~~</figure>~~
	244	+	![](/wiki-images/b/b0/Configure_androidlcl_libraries.jpg)
254	245
255	246		The actual lazarus release contains a error, they create a .so.so - file instead of a .so - file. So you have to change this manually in lazarus.
256	247
257	248		Step 4 - Build the APK
258	249
259	250		If you are using Windows, use these instructions to build the APK: [[Custom Drawn Interface/Android\|Custom Drawn Interface/Android#Step_4_-_Creating_the_APK_package_in_Windows]]
260	251
261	252		If you are using Linux follow these instructions instead: Before going to the command line to build the APK open the file lazarus/examples/androidlcl/android/local.properties and change it to reflect your Android SDK path. The file says you should not modify it, but ignore that and modify it anyway. Here is how the file looks like:
262	253
263	254		# This file is automatically generated by Android Tools.
264	255		# Do not modify this file -- YOUR CHANGES WILL BE ERASED!
265	256		#
266	257		# This file must NOT be checked in Version Control Systems,
267	258		# as it contains information specific to your local configuration.
268	259
269	260		# location of the SDK. This is only used by Ant
270	261		# For customization when using a Version Control System, please read the
271	262		# header note.
272	263		sdk.dir=/home/felipe/Programas/android-sdk-linux
273	264
274	265		After configuring that one, go to the command line and issue these commands:
275	266
276	267		` cd lazarus/examples/androidlcl/android`\
277	268		` ant debug`
278	269
279	270		The APK will be located in lazarus/examples/androidlcl/android/bin
280	271
281	272		Step 5 - Install the APK in your phone and run it
282	273
283	274		You can install via ADB or by copying the file to the sdcard. You should see this:
284	275
285		-	~~<figure>~~
286		-	~~<img src="lcl_android_30_mar.png" title="lcl_android_30_mar.png" />~~
287		-	~~<figcaption>lcl_android_30_mar.png</figcaption>~~
288		-	~~</figure>~~
	276	+	![](/wiki-images/4/4c/Lcl_android_30_mar.png)
289	277
290	278		## How to create an LCL Android Application
291	279
292	280		To create a new LCL-CustomDrawn-Android application simply copy all of the file structure and build and java files from the example project called "androidlcl". This example can be obtained from the Lazarus source tree in lazarus/examples/androidlcl
293	281
294	282		Then you will need to modify the build files to change them to your new project name and your new Java package name.
295	283
296	284		### Step 1 - Creating the LPI
297	285
298	286		You need a separate LPI at the moment for the Android version of the application but all the rest of the code can be shared. Create it using the template for a "Library" and then adapt the code from the example located in the lazarus source code in lazarus/examples/androidlcl
299	287
300	288		You need to adapt the exported JNI method names to your Android Package Name.
301	289
302	290		### Step 2 - Building the library
303	291
304	292		First of all, build the Pascal executable without debug information. This debug information is not so useful in Android and makes the executable much bigger. Open the menu Project-\>Project Options and set the build mode, widgetset, architecture and operating system targets, as shown in these screenshots:
305	293
306		-	~~<figure>~~
307		-	~~<img src="Android_project_options_1.png" title="Android_project_options_1.png" />~~
308		-	~~<figcaption>Android_project_options_1.png</figcaption>~~
309		-	~~</figure>~~
	294	+	![](/wiki-images/6/64/Android_project_options_1.png)
310	295
311		-	~~<figure>~~
312		-	~~<img src="Android_project_options_2.png" title="Android_project_options_2.png" />~~
313		-	~~<figcaption>Android_project_options_2.png</figcaption>~~
314		-	~~</figure>~~
	296	+	![](/wiki-images/f/f7/Android_project_options_2.png)
315	297
316		-	~~<figure>~~
317		-	~~<img src="Android_project_options_3.png" title="Android_project_options_3.png" />~~
318		-	~~<figcaption>Android_project_options_3.png</figcaption>~~
319		-	~~</figure>~~
	298	+	![](/wiki-images/9/9f/Android_project_options_3.png)
320	299
321	300		### Step 3 - Create the Android project structure
322	301
323	302		Besides the LCL project building, such as configuring a proper LPI and having a library main project file, one also needs to add all of the android project structure. Simply copy from the example project in lazarus/examples/androidlcl and adapt it to the new project. Things to change are the path to the SDK, the package name. The package name needs to be updated in the build files, in the directory structure android/src/packagename, in the activity java source code and also in the main library pascal source in the exports section.
324	303
325	304		### Step 4 - Creating the APK package
326	305
327	306		#### Step 4 - Creating the APK package in Linux
328	307
329	308		To create the APK package in Linux simply go to the directory "android" inside the project folder and issue the command "ant debug". The package will be in android/bin/MyProject.apk
330	309
331	310		`cd myproject/android ant debug`
332	311
333	312		Ant and all dependencies must be installed using the package management of your linux distribution.
334	313
335	314		#### Step 4 - Creating the APK package in Windows
336	315
337	316		Pre-requisites:
338	317
339	318		- Java JDK installed: <http://www.oracle.com/technetwork/java/javase/downloads/index.html>
340	319		- Android SDK Installed
341	320
342	321		Instructions:
343	322
344	323		In Windows we provide a APK build system which uses only the tools provided in the Android SDK and therefore does not require ANT.
345	324
346	325		First it is necessary to create a debug key to use. To do this use this script:
347	326
348	327		`lazarus/examples/androidlcl/android/generate_debug_key.bat`
349	328
350	329		which can be copied from the example application to your own project folder.
351	330
352	331		it contains following:
353	332
354	333		`REM Adjust these paths to yours`\
355	334		`SET PATH=C:\Programme\Android\android-sdk\tools;C:\Programme\Android\android-sdk\platform-tools\;C:\Programme\Java\jdk1.6.0_38\bin`\
356	335		`SET APP_NAME=androidlcltest`\
357	336		`SET ANDROID_HOME=C:\Programme\Android\android-sdk`\
358	337		`SET APK_SDK_PLATFORM=C:\Programme\Android\android-sdk\platforms\android-9`\
359	338		`SET APK_PROJECT_PATH=C:\Programme\lazarus\examples\androidlcl\android`\
360		-	\
	339	+
361	340		`mkdir bin`\
362		-	\
	341	+
363	342		`keytool --help`\
364		-	\
	343	+
365	344		`keytool -genkey -v -keystore bin\LCLDebugKey.keystore -alias LCLDebugKey -keyalg RSA -validity 10000`\
366		-	\
	345	+
367	346		`REM call and pause together allow us to see the results in the end`\
368	347		`pause`\
369	348
370	349		You have to fix everything after SET to your own paths. Don't forget adjusting the android version from APK_SDK_PLATFORM!
371	350
372	351		After generating the key, use the other script:
373	352
374	353		`lazarus/examples/androidlcl/android/build_debug_apk.bat`
375	354
376	355		To build the APK file. Also remember to edit this batch file to reflect your paths.
377	356
378	357		This script contains the following:
379	358
380	359		`REM Adjust these paths to yours`\
381	360		`SET PATH=C:\Programme\Android\android-sdk\tools;C:\Programme\Android\android-sdk\platform-tools\;C:\Programme\Java\jdk1.6.0_38\bin`\
382	361		`SET APP_NAME=androidlcltest`\
383	362		`SET ANDROID_HOME=C:\Programme\Android\android-sdk`\
384	363		`SET APK_SDK_PLATFORM=C:\Programme\Android\android-sdk\platforms\android-9`\
385	364		`SET APK_PROJECT_PATH=C:\lazarus\examples\androidlcl\android `\
386		-	\
	365	+
387	366		`REM Create necessary directory Structure`\
388	367		`mkdir bin`\
389	368		`mkdir bin\classes`\
390	369		`mkdir gen`\
391	370		`mkdir gen\com`\
392	371		`mkdir gen\com\pascal`\
393	372		`mkdir gen\com\pascal\lcltest`\
394	373		`mkdir raw`\
395	374		`mkdir raw\lib`\
396	375		`mkdir raw\lib\armeabi`\
397		-	\
	376	+
398	377		`REM Cleanup`\
399	378		`del bin\%APP_NAME%.ap_`\
400	379		`del bin\%APP_NAME%.apk`\
401	380		`del raw\lib\armeabi*.so`\
402		-	\
	381	+
403	382		`REM More directory preparation`\
404	383		`copy libs\armeabi*.so raw\lib\armeabi\ `\
405		-	\
	384	+
406	385		`REM Resource compilation`\
407	386		`call aapt p -v -f -M AndroidManifest.xml -F bin\%APP_NAME%.ap_ -I %APK_SDK_PLATFORM%\android.jar -S res -m -J gen raw`\
408		-	\
	387	+
409	388		`REM Java compiler`\
410	389		`call javac -verbose -classpath %APK_SDK_PLATFORM%\android.jar -d bin\classes src\com\pascal\lcltest\LCLActivity.java`\
411		-	\
	390	+
412	391		`REM DX to convert the java bytecode to dalvik bytecode`\
413	392		`call dx --dex --verbose --output=%APK_PROJECT_PATH%\bin\classes.dex %APK_PROJECT_PATH%\bin\classes `\
414		-	\
	393	+
415	394		`REM It seams that dx calls echo off`\
416	395		`@echo on`\
417	396		`REM Now build the unsigned APK`\
418	397		`del %APK_PROJECT_PATH%\bin\%APP_NAME%-unsigned.apk`\
419	398		`call apkbuilder %APK_PROJECT_PATH%\bin\%APP_NAME%-unsigned.apk -v -u -z %APK_PROJECT_PATH%\bin\%APP_NAME%.ap_ -f %APK_PROJECT_PATH%\bin\classes.dex`\
420		-	\
	399	+
421	400		`REM Generating on the fly a debug key`\
422	401		`rem keytool -genkey -v -keystore bin\LCLDebugKey.keystore -alias LCLDebugKey -keyalg RSA -validity 10000 -dname NAME -storepass senhas -keypass senhas`\
423		-	\
	402	+
424	403		`REM Signing the APK with a debug key`\
425	404		`del bin\%APP_NAME%-unaligned.apk`
426	405
427	406		`REM Change keypass and storepass pw here\| and here\|`\
428	407		`jarsigner -verbose -keystore bin\LCLDebugKey.keystore -keypass senhas -storepass senhas -signedjar bin\%APP_NAME%-unaligned.apk bin\%APP_NAME%-unsigned.apk LCLDebugKey`\
429		-	\
	408	+
430	409		`REM Align the final APK package`\
431	410		`zipalign -v 4 bin\%APP_NAME%-unaligned.apk bin\%APP_NAME%.apk `\
432		-	\
	411	+
433	412		`REM call and pause together allow us to see the results in the end`\
434	413		`pause`
435	414
436	415		Don't forget changing the set-variables in the top AND change the pw (see above where).
437	416
438	417		### Building an LCL Android application with debug info
439	418
440	419		It is useful to add another Android build mode which has debug info. Use all of the same options as shown above, except for the debug information:
441	420
442		-	~~<figure>~~
443		-	~~<img src="Android_project_options_4.png" title="Android_project_options_4.png" />~~
444		-	~~<figcaption>Android_project_options_4.png</figcaption>~~
445		-	~~</figure>~~
	421	+	![](/wiki-images/1/11/Android_project_options_4.png)
446	422
447	423		## Oh no! My LCL Android application doesn't work
448	424
449	425		There are various reasons why the app may not work. The most important thing to do when an app doesn't work is to open the logcat and see what the log says. This can be done by running this command line command:
450	426
451	427		``` bash
452	428		./adb logcat
453	429		```
454	430
455	431		And then test one of the hypotheses in the next subsections.
456	432
457	433		### The Pascal executable was compiled for a wrong architecture, operating system and/or widgetset
458	434
459	435		This is the leading cause of executables not running. Always verify that you compiled the program to the "android" widgetset, "linux" operating system and "arm" architecture. This is done by going into the menu Project-\>Project Options. Then set these in the dialog all options as explained in this section:
460	436
461	437		[[How to build an LCL Android application]]
462	438
463	439		To check if you library is arm-linux or not, execute the following commands:
464	440
465	441		``` bash
466	442		cd libs/armeabi
467	443		ls -l
468	444		file liblclapp.so
469	445		ldd liblclapp.so
470	446		```
471	447
472	448		If it mentions anything like 80386 or gtk, then your program was compiled for linux-x86 and gtk2, not for Android like it should.
473	449
474	450		### My Pascal application crashed. How to get a stacktrace?
475	451
476	452		If a Pascal application crashes you should use the command "adb logcat" to obtain the stack
477	453
478	454		Read also this thread in the Google NDK group about converting addresses to lines: <http://groups.google.com/group/android-ndk/msg/2ed2286e85f4ccdd>?
479	455
480	456		### The indispensable build options
481	457
482	458		- -Xd This build option is indispensable when cross-compiling from x86-linux to Android or else FPC will try to link the application against for example /usr/lib/libc.so instead of the libc.so in the NDK, even if you specify a -Fl library path
483	459		- -CpARMV6 This build option is indispensable because code generated for older ARM versions is unsupported by Android and might crash in some devices. See <http://groups.google.com/group/android-ndk/browse_thread/thread/ba542483f062a828>
484	460		- -dAndroid in the package LCLBase.lpk
485	461		- -Parm -Tlinux for the process and target operating system
486	462		- -Fl should contain the path to the NDK directory with the target link shared object, such as libc.so, liblog.so, libjni.so, etc
487	463
488	464		### Wrong package name
489	465
490	466		If you change the package name of the project, then you need to adapt the main project file to inform the widgetset of the change. In the example project this is done in the main project file, androidlcltest.lpr in this part:
491	467
492	468		CDWidgetset.ActivityClassName := 'com/pascal/lcltest/LCLActivity';
493	469
494	470		If your new package name is com.pascal.myapp, then you should change the command above to this:
495	471
496	472		CDWidgetset.ActivityClassName := 'com/pascal/myapp/LCLActivity';
497	473
498	474		## Free Pascal Bugs on Android Support
499	475
500	476		The following summarizes the state of Android Support in Free Pascal:
501	477
502	478		- The pre-compiled snapshot for x86-linux -\> Android is known to work very well and it was built on 19th January 2011: <https://sourceforge.net/projects/p-tools/files/Free%20Pascal%20for%20ARM/>
503	479		- On February this revision <http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=rev&revision=16981> introduced this bug: <http://mantis.freepascal.org/view.php?id=18833>
504	480		- In the end of 2011 this revision <http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=rev&revision=19036> broke linking Android projects
505	481
506	482		We are in contact with FPC developers to fix the situation as can be seen in: <http://mantis.freepascal.org/view.php?id=20726>
507	483
508	484		### FPC4Android Branches
509	485
510	486		Because of FPC bugs related to Android support I have rolled my own branches.
511	487
512	488		#### FPC4Android 2.5.1
513	489
514	490		FPC4Android 2.5.1 has the following fixes applied to it:
515	491
516	492		<http://bugs.freepascal.org/view.php?id=21208> <http://bugs.freepascal.org/view.php?id=21341> <http://bugs.freepascal.org/view.php?id=19559>
517	493
518	494		And I have created a pre-compiled x86-linux -\> android-arm cross-compiler and hosted it here (it is the -v2 cross-compiler);
519	495
520	496		<https://sourceforge.net/projects/p-tools/files/Free%20Pascal%20for%20ARM/>
521	497
522	498		To download the source execute:
523	499
524	500		`svn co `[`https://p-tools.svn.sourceforge.net/svnroot/p-tools/fpc4android`](https://p-tools.svn.sourceforge.net/svnroot/p-tools/fpc4android)` fpc4android`
525	501
526	502		#### FPC4Android 2.6.1
527	503
528	504		This branch is not finished, it lacks patches to fix Android support, patches are welcome. SVN link:
529	505
530	506		`svn co `[`https://p-tools.svn.sourceforge.net/svnroot/p-tools/fpc4android_2_6`](https://p-tools.svn.sourceforge.net/svnroot/p-tools/fpc4android_2_6)` fpc4android_2_6`
531	507
532	508		## Android SDK and NDK bugs
533	509
534	510		### Android NDK for Windows broken linker
535	511
536	512		The linker in android-ndk-r7b (path C:\Programas\android-ndk-r7\toolchains\arm-linux-androideabi-4.4.3\prebuilt\windows\bin\arm-linux-androideabi-ld.exe) crashes for no reason while linking LCL apps =( The linker from android-ndk-r7 and r5 work correctly.
537	513
538	514		See <http://groups.google.com/group/android-ndk/browse_thread/thread/d8c88bd58ad6df87>
539	515
540	516		### Error while calling DX: Trouble processing: bad class file magic (cafebabe)
541	517
542	518		If while using the build script you get the following errors:
543	519
544	520		D:\djsystem\djpalm\android>call dx --dex --verbose --output=D:\djsystem\djpalm\a
545	521		ndroid\bin\classes.dex D:\djsystem\djpalm\android\bin\classes
546	522		processing D:\djsystem\djpalm\android\bin\classes\.\com\pascal\djpalm\LCLActivit
547	523		y$1.class...
548	524
549	525		trouble processing:
550	526		bad class file magic (cafebabe) or version (0033.0000)
551	527		...while parsing com/pascal/djpalm/LCLActivity$1.class
552	528		...while processing com/pascal/djpalm/LCLActivity$1.class
553	529		processing D:\djsystem\djpalm\android\bin\classes\.\com\pascal\djpalm\LCLActivit
554	530		y$2.class...
555	531
556	532		trouble processing:
557	533		bad class file magic (cafebabe) or version (0033.0000)
558	534		...while parsing com/pascal/djpalm/LCLActivity$2.class
559	535		...while processing com/pascal/djpalm/LCLActivity$2.class
560	536		processing D:\djsystem\djpalm\android\bin\classes\.\com\pascal\djpalm\LCLActivit
561	537		y$3.class...
562	538
563	539		This probably means that you are using JDK 7. Unfortunatelly the current Android SDK r20 is not compatible with JDK 7, only with JDK 5 and 6. Please install JDK 6 and use that instead. See:
564	540
565	541		- <http://stackoverflow.com/questions/8538891/bad-class-file-magic-when-using-dx-bat>
566	542		- <http://www.oracle.com/technetwork/java/javase/downloads/jdk6-downloads-1637591.html>
567	543
568	544		## Development Notes
569	545
570	546		### The mysterious JNI Crash
571	547
572	548		See the thread: <http://groups.google.com/group/android-ndk/browse_thread/thread/ba542483f062a828>
573	549
574	550		The problem was that vm^^.GetEnv would crash in HTC Wildfire, Alcatel and in the emulator with SIGILL but not in Xperia Mini, HTC Desire HD, Motorola Atrix and other smartphones.
575	551
576	552		The answer was that one needs to specify -CpARMV6 when building because older instructions might fail in some devices
577	553
578	554		### NDK Libraries available in Android 2.2 (API level 8)
579	555
580	556		LCL-CustomDrawn targets Android 2.2+ and in this API level the following libraries are supported by the NDK:
581	557
582	558		1. libc.so
583	559		2. libdl.so (linker)
584	560		3. OpenGL ES 1
585	561		4. OpenGL ES 2
586	562		5. libjnigraphics.so
587	563		6. liblog.so
588	564		7. libm.so
589	565		8. libz.so
590	566		9. libthread_db.so
591	567		10. libstdc++.so
592	568
593	569		LCL-CustomDrawn-Android uses libjnigraphics.so and liblog.so at the moment.
594	570
595	571		### Native text drawing
596	572
597	573		Native text drawing is a bit convoluted in Android and the documentation is quite bad too. Some gotchas already found:
598	574
599	575		- It draws text starting on a Y coordinate which represents the baseline, which is the bottom of strings like "abc", but not the bottom of strings like "qg". See <http://code.google.com/p/android/issues/detail?id=393>
600	576		- There is no documentation about what the size in Paint.setTextSize represents. Some people say it is pixels, but to me it looks something else because it seams to differ across devices.
601	577
602	578		But there are also good things about it:
603	579
604	580		- It can draw on a transparent bitmap and use alpha transparency to implement anti-aliasing and subpixel rendering. The text gets quite beaultiful.
605	581		- It can draw on the ARGB 32-bits non-premultiplied format which is a pretty good one
606	582
607	583		### Flood of garbage collector messages when the caret is visible
608	584
609	585		Something like this:
610	586
611	587		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 188 objects / 6664 bytes in 94ms
612	588		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 170 objects / 6160 bytes in 78ms
613	589		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5904 bytes in 82ms
614	590		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5856 bytes in 78ms
615	591		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5872 bytes in 80ms
616	592		D/dalvikvm( 2825): GC_EXPLICIT freed 371 objects / 18480 bytes in 91ms
617	593		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5896 bytes in 78ms
618	594		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5896 bytes in 78ms
619	595		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5896 bytes in 81ms
620	596		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5920 bytes in 78ms
621	597		D/dalvikvm( 6364): GC_EXTERNAL_ALLOC freed 162 objects / 5920 bytes in 83ms
622	598
623	599		In my investigation this happens probably because the TCDEdit will request a full control invalidate on each timer tick, which currently will main a full form invalidate, so the GC needs to collect the bitmaps and other paint objects when painting that often.
624	600
625	601		### Why the caret of a TEdit keeps blinking after clicking on the form
626	602
627	603		When clicking on the form the LCL focus will refuse to move from the Edit to the Form because this behavior seems to be hard coded in the LCL, although maybe we might change this for Android. So even while we set focus into the form, the LCL refuses to do that and keeps its focus in the Edit, thus we have a focus mismatch. This might eventually be fixed in the future.
628	604
629	605		### Android ComboBox
630	606
631	607		For adding Android combobox support a new method was added to LCLIntf along with a global variable to store the callback of this dialog:
632	608
633	609		``` pascal
634	610		var
635	611		OnShowSelectItemDialogResult: TOnShowSelectItemDialogResult;
636	612
637	613		function ShowSelectItemDialog(const AItems: TStrings): Boolean; override;
638	614		```
639	615
640	616		This method will run a native item selection dialog, if the platform has one, or result false without doing anything otherwise.
641	617
642		-	~~<figure>~~
643		-	~~<img src="Android_combobox.png" title="Android_combobox.png" />~~
644		-	~~<figcaption>Android_combobox.png</figcaption>~~
645		-	~~</figure>~~
	618	+	![](/wiki-images/8/82/Android_combobox.png)
646	619
647	620		### Using the Native ListView Dialog
648	621
649	622		To allow the user to select items from a list more easily we offer a routine which launch dialog with the native ListView.
650	623
651	624		``` pascal
652	625		{$ifdef LCLCustomDrawn}
653	626		uses customdrawnint, lclintf;
654	627		{$endif}
655	628
656	629		procedure TForm2.Button3Click(Sender: TObject);
657	630		begin
658	631		{$ifdef LCLCustomDrawn}
659	632		LCLIntf.OnListViewDialogResult := @MyOnListViewDialogResult;
660	633		CDWidgetSet.ShowListViewDialog('Dialog Title',
661	634		['Title1', 'Title2', 'Title3', 'Title4', 'Title5', 'Title6'],
662	635		['Descr1', 'Descr2', 'Descr3', 'Descr4', 'Descr5', 'Descr6']);
663	636		{$endif}
664	637		end;
665	638
666	639		procedure TForm2.MyOnListViewDialogResult(ASelectedItem: Integer);
667	640		begin
668	641		DebugLn(Format('[MyOnListViewDialogResult] ASelectedItem=%d', [ASelectedItem]));
669	642		end;
670	643		```
671	644
672	645		LCLIntf.OnListViewDialogResult will be called with the selected item, with a zero-based index, or -1 if the dialog was cancelled by the user. One way to cancel the dialog is when the user pressed the back button.
673	646
674	647		Note that there are 2 more parameters in the end of this routine with default values, which allow choosing the color for the odd and the other for the even rows. The color is an integer of 32-bits in the ARGB format, don't use TColor here!
675	648
676	649		``` pascal
677	650		procedure TCDWidgetSet.ShowListViewDialog(ATitle: string; ATitles,
678	651		ADescriptions: array of string;
679	652		AColorOddRow: jint = $ff292C29; AColorEvenRow: jint = $ff424542);
680	653		```
681	654
682		-	~~<figure>~~
683		-	~~<img src="Android_ListView.png" title="Android_ListView.png" />~~
684		-	~~<figcaption>Android_ListView.png</figcaption>~~
685		-	~~</figure>~~
	655	+	![](/wiki-images/2/2c/Android_ListView.png)
686	656
687	657		### LazDeviceAPIs
688	658
689	659		See: [[LazDeviceAPIs]]
690	660
691	661		---
692	662		From the Free Pascal wiki, page "Custom Drawn Interface/Android/ja", as it stood on 2021-01-08 after a change by Giorgio Tani, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).

Back to history