Eclipse Android source code engineering debugging

Eclipse AndroidSource code engineering debugging is the content to be introduced in this article, mainly to understand and learnEclipse AndroidThe content of the source code.Eclipse AndroidFor more information about the source code, see this article.

1. Compile the source code in ubuntu

It is best to switch to the root user for operations

 
 

  
  
$ sudo -s 
 
 

1) download and install jdk1.5 (download the self-decompressed version and set the environment variables)

Edit/root/. bashrc add

 
 

  
  
#set java environment  
  
  
export JAVA_HOME=/work/jdk1.5.0_22  
  
  
export JRE_HOME=JAVA_HOME/jre  
  
  
export CLASSPATH=$JAVA_HOME/lib:$JRE_HOME/lib:$CLASSPATH  
  
  
export SDK_HOME=/work/froyo/out/host/linux-x86/sdk/android-sdk_eng.root_linux-x86/tools  
  
  
export PATH=$JAVA_HOME/bin:$JRE_HOME/bin:$PATH:$SDK_HOME:/work/froyo/out/host/linux-x86/bin  
  
  
export ANDROID_PRODUCT_OUT=/work/froyo/out/target/product/generic 
 
 

2) install (apt-get install xxx)

 
 

  
  
git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev 
 
 

3) download the source code (detailed instructions on the Internet)

4) Compile the source code

 
 

  
  
$ export ANDROID_JAVA_HOME=$JAVA_HOME  
  
  
$ make 
 
 

Check whether there are any errors during the compilation process. Generally, there are no errors. If there is an error, it may be that a dependency package is not installed. Install the dependent package prompt and re-make

5) generate the sdk

 
 

  
  
$ Make PRODUCT-sdk ### using make sdk, the R file cannot be automatically generated.
 
 

After compilation, the sdk is generated in the/work/froyo/out/host/linux-x86/sdk/directory.

6) check whether the compilation is successful after compilation.

 
 

  
  
$. Build/envsetup. sh
  
  
$ Emulator & // start the simulator. If it can be started successfully, the compilation is successful.
 
 

2. debugging in Android Eclipse

1) Copy development/ide/eclipse/. classpath to the source code root directory and modify. classpath.

Delete the following two rows

 
 

  
  
<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="/work/froyo/out/target/common/obj/JAVA_LIBRARIES/android-common_intermediates/javalib.jar"/> 
 
 

2) modify it in eclipse

2.1) use create project from existing source to import froyo source code

2.2) Expand packages/providers/CalendarProvider/src

2.3) Expand the package: com. android. providers. calendar

2.4) Right-click the package com. android. providers. calendar

2.5) Select "new file"

2.6) in the dialog box, click "Advanced>" to see "Link to file in the file system" checkbox,

2.7) Check checkbox. Then "Browse..." is available.

2.8) Click "Browse... "button, select EventLogTags. java (e.g ., out/target/common/obj/APPS/CalendarProvider_intermediates/src/com/android/providers/calendar/EventLogTags. java)

2.9) Click OK

2.10) Click Finish (in "New File ")

3) Modify com. android. providers. contacts in the same way.

3. debugging

Modify the source code in IDE (eclipse) and compile and run it in shell.

Built-in compilation tools for source code

Execute. build/envsetup. sh In the Eclipse Android source code root directory, and then compile it through m/mm/mmm.

 
 

  
  
- m:       Makes from the top of the tree.  
  
  
- mm:      Builds all of the modules in the current directory.  
  
  
- mmm:     Builds all of the modules in the supplied directories. 
 
 

 
 

  
  
$ Cd/path/to/android/root
  
  
$. Build/envsetup. sh
  
  
$ Lunch 1 # initialize simulators, etc.
  
  
$ Make/m/mm/mmm #
  
  
$ Emulator & # you shoshould see a GUI picture of a phone
  
  
$ Ddms & # debugging tool
 
 

1) modify the APK application: the application in packages can be compiled independently after modification. Run

 
 

  
  
$. Build/envsetup. sh # Initialization
  
  
$ Mmm packages/providers/ContactsProvider/
  
  
# The. APK compiled with mm/mmmwill not be packaged into system. img. You need to manually package the system folder as system. img through make snod.
  
  
# You can use make snod to package the module into system. img, or use adb install *. apk to install the module.
 
 

Note: After you use mmm packages/providers/ContactsProvider/compiled apk in the out/target/product/generic/system/app

In this case, use adb install out/target/product/generic/system/app/xxx.apk to install the apk you just modified and you will be able to see the modification effect on the simulator.

2) modify the framework: If the framework is modified in Contacts. java, you must re-compile the framework. Run

 
 

  
  
$. Build/envsetup. sh # Initialization
 
 

# If you want to execute make update-api on the Internet, you can directly make PRODUCT-sdk to compile the modified framework into the sdk. # After the framework is compiled, the modified applications do not need to be compiled separately. 4 ~ 6 minutes

 
 

  
  
$ Make PRODUCT-sdk # regenerate SDK 10 ~ 20 minutes.
 
 

Summary: The Eclipse Android source code project debugging is complete. I hope you can learn the Eclipse Android source code to help you.