How to Use Eclipse to develop Android source code

Document directory

• The following describes how to establish an Android development environment and how to use development tools.
• From the official documents and practices, we can summarize the following points:

Use Eclipse to develop Android source code

(This article describes how to develop the Android source code, including the source code of each platform, instead of the source code released by Google. I use msm3167.

The SDK is not required and the ADT is not required. It can be generated through the compilation of the entire project. To debug the source code in Eclipse, such as Phone, MMS, and Contact ......

Since I have never touched on Java, Eclipse, ADT..., I have read more than N Articles on the Internet. In this article, I posted them for sharing and added them,

Configure the TroubShooting. If you are new to Android, you may not be able to configure these settings at half past one, so be prepared.

Official Website: http://source.android.com/source/using-eclipse.html

Start with a question

1. What is the structure of the Android file system? Where are the installed programs?
After the Android source code is compiled, some files in out/target/product/generic:
Ramdisk. img, system. img, userdata. img, system, data, root
Here, system. img is packaged and compressed by system, and userdata. img is packaged and compressed by data.

Ramdisk. img is the file system of the simulator. After extracting ramdisk. img, you can see that the files in ramdisk. img are basically the same as those in the root folder.
The simulator loads ramdisk. img and decompress it To the memory. Then, the system. img and userdata. img are mounted to the system and data directories under ramdisk respectively. The compiled application is stored in system/app. The programs installed by the user are stored in data/app.

2. What tools does the Android SDK and android Source Code provide for us?
The Android SDK provides many tools, such as adb, ddms, emulator, and aapt. It also provides kernel-qemu, ramdisk. img, system. img, and userdata. img. Therefore, with the android SDK, we can run android on the simulator.
Android source code can compile android SDK, adb, and other tools, android file systems, and ADT plug-ins. That is to say, we can compile all android-related things from android source code.

3. Many tools and Android file systems (system. img, etc.), and we can use the "make sdk" to generate the android SDK. The android SDK also includes tools and the android File system (system. img, etc.), and we also installed the android SDK during the original installation, So what tools and android file systems should we use during development?
This question will be answered later.

4. We officially recommend using eclipse + adt to develop applications. Our HelloActivity program is also developed here. When we import the project under the Android source code/packages/apps/into eclipse, the error that cannot find the package usually occurs. So how can we modify, compile, and debug the android source code? What tools does Google use to develop android?
This question will be answered later.

The following describes how to establish an Android development environment and how to use development tools.

I. Installation of Android SDK and eclipse and establishment of android Development Environment
Android tool chain is relatively complete and requires fewer external tools. For more information about the installation process, see the official documentation or <android simulator installation in Ubuntu8.10> and <android source code compilation>.
Note that when "make" is used to compile the Android source code, JDK 5 or JDK 6 can be used. When "make sdk" is used to compile the code, javadoc is used to generate the document, javadoc of JDK 5 must be used; otherwise, the compilation will fail. Therefore, we can install JDK5 and jdk6, and then point javadocand javadoc.1.gz to corresponding tools of jdk5. other tools still use jdk6. Of course, we can only install JDK 5 or only use JDK 5. For more information, see <android source code compilation>

2. Use eclipse to develop Android source code
For more information, see the official documentation.

Https://sites.google.com/a/Android.com/opensource/using-eclipse

Next, we will summarize from the official documents how to use eclipse to develop the Android source code.

1. Establish a basic Android Development Environment
Please refer to the official documentation or <Android simulator installation in Ubuntu8.10>

2. Compile the Android source code
Use make to compile the Android source code in the root directory. Pay attention to some configurations. For more information, see <android source code compilation>

3. Copy the eclipse project configuration file to the root directory of the Android source code.
Cp development/ide/eclipse/. classpath ./
Chmod u + w. classpath # Make the copy writable
4. modify the configuration of the eclipse Program
1) Increase eclipse memory settings
Change the three values of eclipse. ini (under the eclipse installation directory) to the following values:
-Xms128m
-Xmx512m
-XX: MaxPermSize = 256 m
2), the Android-formatting.xml and android. importorder into eclipse (optional)
The Android-formatting.xml,. classpath, and android. importorder are all placed in the development/ide/eclipse/
Android-formatting.xml is used to configure the code style of the eclipse editor; android. importorder is used to configure the order and structure of the eclipse import.
Import Android-formatting.xml in window-> preferences-> java-> Code style-> Formatter
Import Android. importorder to window> preferences> java> Code style> Organize Imports.
3) install the anyedit plug-in (optional)
Download and import data to eclipseat at http://andrei.gmxhome.de/anyedit/

5. Import the Android source code as a project into eclipse
Check Before importing. whether the files in classpath have corresponding files (folders) in the Android source code; otherwise, the android source code will be damaged (usually multiple files/folders are added ),. the redundant paths in classpath can be deleted.
Create a Java Project (not an Android project; otherwise, the android source code will be damaged). Select www.linuxidc.com to import the existing Project. The project name is arbitrary and complete.
It is slow to build a project in eclipse during import. After the import, there are generally no errors.
4th questions are answered here

 

Note:

1. creating a new java project step will also cause parsing errors. My eclipse cannot select to import from an existing project when creating a new java project. Therefore, take the following steps to first create and import the project:

New: New java project

 

Project name
Enter

If the default location is not used, specify the Location as the Code directory, that is

Uncheck "use default location", select the project root directory for Location (this must be selected, otherwise the package list will have an error), click Finish,
It takes some time to start building the workspace .....

Import: File-> Import-> select, General select Exiting projects into workspace,-> Next select the source code root directory, and Finish.

All associated source codes are listed in packageExplorer of eclipse.

 

2. If there is an error in parsing, debugging will fail. The biggest problem I encountered is that there is an error in the problem window in eclipse. The following is a solution.

Delete the following two rows of. classpath

<Classpathentry kind = "lib" path = "out/target/common/obj/JAVA_LIBRARIES/google-common_intermediates/javalib. jar"/>
<Classpathentry kind = "lib" path = "out/target/common/obj/JAVA_LIBRARIES/gsf-client_intermediates/javalib. jar"/>
Add

<Classpathentry kind = "lib" path = "out/target/common/obj/JAVA_LIBRARIES/android-common_intermediates/javalib. jar"/>

At this time, an error occurs in EventLogTags in the CalendarProvider and ContactProvider, and then modify the following:

1. Expand packages/providers/CalendarProvider/src
2. Expand the package: com. android. providers. calendar
3. Right-click the package com. android. providers. calendar
4. Select "new file"
5. Click "Advanced>" in the dialog box to see "Link to file in the file system" checkbox,
6. Check checkbox. Then "Browse..." is available.
7. click "Browse... "button, select EventLogTags. java (e.g ., out/target/common/obj/APPS/CalendarProvider_intermediates/src/com/android/providers/calendar/EventLogTags. java)
8. Click OK.
9. Click Finish (in "New File ")
Modifying com. android. providers. contacts in the same way

In this way, eclipse only has warning to parse the entire source code.

 

 

 

6. debug the Android program on eclipse.
To prevent other versions of Android tools and android file systems from affecting compilation and debugging, you need to remove the paths of android tools and android file systems from the environment variables:
Vim ~ /. Bashrc
Check whether the PATH of the Android tool and android file system is added to the PATH variable. If yes, comment it out. In the following method, we do not need to add the path of the android tool and the android File System to. bashrc.
Run:
Cd Android source code directory

. Build/envsetup. sh # After the environment variable is set, mmm and other commands will be added. You can enter help to view
Lunch 1 # maps emulator and other tools with the paths of files such as ramdisk. img, you can directly call emulator and other tools, and solve 3rd Problems
Emulator &
Ddms &
Note: first start ddms and then start eclipse, so that there will be no port conflict in eclipse.
Configure the debugging type and port in eclipse:
Double-click Run-> Debug deployments-> Remote java application and set "Host:" to localhost and "Port:" To 8800, "Connection Type" is Standard (Socket Attach)
Then "Apply"
Note: The Port set above must be consistent with the Port set in DDMS (view the path File --> Preference, select Debugger on the left, and Port of Selected Port on the right, the ADT plug-in uses port 8700, so the port set above is 8800. If the VM cannot be connected, you must select a process (corresponding to an application) in DDMS ), debug can be executed in eclipse (in the Java view, click Open Perspective at Right-top and select debug to enter the debug window ).

 

 

 

With my debugging experience:

The error "Failed to connect to remote VM" is often prompted according to the above steps. The cause is the port configuration problem above.

First, select a debug process in ddms. Click a process and you will see a green bug icon before the process displayed in ddms.
Write down the Port of the process (which can be seen in the last column of ddms) and configure the Port in remote java application.
If Port 8700 is used for debugging, it indicates that you will debug the selected ddms process. You have not selected any process in ddms, so ClosedConnectionException will pop up.
See http://source.android.com/source/using-eclipse.html:
Note that port 8700 is attached to whatever process is currently selected in the DDMS console, so you need to sure that DDMS has selected the process you want to debug.
(Note that port 8700 is used to debug any process selected in DDMS. Therefore, you must confirm that the process you want to debug has been selected in DDMS .)

 

 

During eclipse debugging, you can set breakpoints and perform one-step debugging. For more information about how to debug them, see

Http://blog.csdn.net/lixnhollycrmcom/archive/2011/03/23/6271853.aspx

It is estimated that the google team developed and debugged Android applications in this way.

7. Compile the Android source code
Run:
Cd Android source code directory
. Build/envsetup. sh
Then there will be more commands such as mm/mmm. mm/mmm is used to compile modules (including C, C ++, and JAVA programs ). We can also directly
Run "make Module name" in the root directory of the Android source code to compile the module (the module name can be found in the. mk file ). After the module is compiled, it will generate a corresponding .apk package under out/target/product/generic/system/app. However, the. APK compiled with mm/mmmwill not be packaged into the system. in img, We need to manually package the system folder as system through make snod. img, but you have to re-run the simulator, which is also very troublesome. For our developers, we can do this:
1. Remove the modified versions (such as alarmclock.apk) from/system/app, and then make snod,system.imghas no alarmclock.apk.
2) run the simulator and you will not be able to see AlarmClock.
3) modify the source code of AlarmClock and compile it with mm/mmm. Then, generate alarmclock.apk under/system/app.
4. Install alarmclock.apk to the Android file system through adb. there are two installation methods:
A. Run adb install xxx/AlarmClock.apk
B. push xxx/AlarmClock.apk/data/app through adb
You can install AlarmClock under/data/app. androidwill automatically display the lock in the main menu (only alarmclock.apk contains an Activity package containing android. intent. category. LAUNCHER attribute), but method A generates com.android.alarmclock.apk in/data/app, and method B generates AlarmClock.apk. When using method A, if AlarmClock has been installed, you must first adb uninstall it, and method B does not need. The B method is recommended. Similarly, you can use the adb
Uninstall or adb shell rm xxx/xxx.apk. We recommend that you use the delete method to uninstall the SDK.

8. How to develop your own projects
The previous section mainly describes how to develop the original Android project on eclipse. For our own projects, we can do this:
1) Create an Android project.
The advantage of building an Android project is that you can make full use of the ADT function.
2) import the required package
3) Compile, run, and debug
4) Add the app to the corresponding Android source code Directory, which is usually stored in packages/apps.
When we observe the original project of packages/apps, we will find that their code is "clean", without folders such as assets and bin automatically generated by ADT and R. java, of course not. classpath and. project
5) write the Makefile xxx. mk.
The dedicated Makefile xxx. mk provided by the Android source code is in a simple format.
6) Add the newly added project to the Android project of eclipse
You can add a path in eclipse or in. classpath. For example, add the following content to. classpath:
<Classpathentry kind = "src" path = "packages/apps/HelloWorld/src"/>
R. java is automatically generated during compilation. In fact, all projects that use "Resources" will use R. java. These R. java files are placed under out/target/common/R. During makefull code under the source code root directory, modules that have been compiled and generated with .apk files will not be compiled for each worker. Therefore, if the newly added project has been compiled (using mm/mmm), we need to change the "resource" of the project first (the "resource" must be changed because R. java is generated by a "resource"), and then make, you will see the R of your project in the package path corresponding to out/target/common/R. java. Refresh out/target/common/R in eclipse
Child project, and then add its package where you use the R class, such
Import com. Android. example. test. inside. helloworld. R.
In fact, this error has no effect on us, because we compile it in shell.
7) Compile the newly added project in the Android source code directory.
You can use the mm/mmm Or make Module name.
8) Use a version control tool (svn, git, or other) to upload the project to the server.

 

From the official documents and practices, we can summarize the following points:

1. You can use eclipse to edit JAVA programs and check for errors (mainly including class library inclusion and syntax). However, you cannot compile and run the Android source code on eclipse, still make (or mm or mmm) in shell)
2. Some eclipse configuration files are provided in the Android source code folder,
. Claapath: the configuration file of the eclipse project, so that we can directly import the file and JAVA package corresponding to the Android source code to the project.
Android-formatting.xml and android. importorder: This is very important, mainly used to regulate our encoding style, it is easier to make our code style consistent
3. When importing the Android source code as a project into eclipse, pay attention to the following two points:
1) the newly created project must be a java project, not an Android project. Otherwise, the android source code will be damaged (generally multiple files/folders are added)
2) check whether the file in. classpath has a corresponding file (folder) in the Android source code before import. Otherwise, the android source code will be damaged (generally add more files/folders)

In general:
1. Use eclipse to edit code and check for errors
2. If you do not compile or run the Android source code program on eclipse, you can only compile the android source code through make (or mm or mmm) on the command line.
3. You can debug the Android source code program on eclipse (Principle: eclipse uses the ddms server to debug on emulator), and can debug and breakpoint in one step.
4. The program to be debugged removes it from/system/app/and installs it under data/app, which is more convenient.
5. It is easier to install and uninstall programs by using adb push and adb shell rm.