My DIY Android journey-first knowledge of android2.3 source code

After compiling and running the android source code, the next step is how to learn the huge Android source code. There is no correct way to learn and analyze it, so you can't figure out the code after several years of estimation. As an android developer, what you need is to extract the part you want from a very large and complex code, then correct it and write it!

Let's talk about the directory structure of the source code (android2.3 ).

Makefile)
Bionic (bionic C library, C runtime support: libc, libm, libdl, dynamic linker)
Bootable (BOOT guide code)
Build (stores basic development kit configurations such as system compilation rules and generic)
CTS (Android compatibility test kit Standard)
Dalvik (Dalvik Java Virtual Machine)
Development (Application Development)
Device (compilation variables of vendor devices, etc)
External (some open-source modules used by Android)
Frameworks (core framework-Java and C ++ language)
Hardware (mainly hardware Adaptation Layer HAL code)
Libcore (core library, supporting Dalvik)
Ndk (a development tool for local code, used to include the local code of the Application)
Out (the code output after compilation is in this directory)
Packages)
Prebuilt (resources pre-compiled in x86 and arm architectures)
SDK (SDK and simulator)
System (File System Library, applications and components-C language)

For detailed directories, refer:

Http://www.oschina.net/question/234345_44376

If you want to develop a driver, you have to download the Kernel File by yourself, because the kernel file in the android source code is a previously compiled image file, not the source code, you need to synchronize the Kernel File on Google and compile the file on your own. In this way, the DIY Android system is true. The source code of many drivers can also be directly compiled into the kernel...

Kernel download method: