Directory Analysis of Android source code PostScript

Source: Internet
Author: User

When Android is compiled, an out folder is generated in the root directory, and all generated content is placed in this folder.

The Out folder looks like this:
out/
--CaseCheck.txt
--Casecheck.txt
--Host//represents the tool generated on the host (x86)
--Common
--Linux-x86/darwin-x86
--Target (indicates the target machine, if the compiler defines target_strip_module=false, this directory is Debug/target)


--Common
--Product
The main two directories are host and Target, which represents the tools generated on the host (x86), which represents the content that the target machine (default is ARMV5) runs.



The structure of the host directory is as follows:
out/host/
--Common
--obj (Java library)
--Linux-x86/darwin-x86
--Bin (binary program)
--Framework (Java Library, *.jar file)
--Lib (Shared library *.so)
--obj (intermediate generated target file)
The host directory is some of the tools used on hosts, some are binaries, and some are Java programs.



The structure of the target directory is as follows:
out/target/
--common//denotes generic content
--R (resource file)
--Docs
--obj (target file)
-Product//content for products
--generic
Where the common directory represents generic content, product is the content of the products.


In the common directory, obj, contains two important directories:

out/target/obj/
--apps (contains the target of Java application generation, each application corresponding to one subdirectory, will be combined with each application's original file to build the Android app apk package)
--java_libraries (contains a library of JAVA, each of which corresponds to one subdirectory)



By default, Android compilation will generate the generic directory if the selected product can also generate additional catalogs (named according to the pre-defined product name).

Generic contains the following content:
out/target/product/generic/
--Data (the file system in which it resides)
--obj (the directory contains a variety of Java applications, as opposed to Common/obj/apps, but has been played APK package)

--Root
--Symbols
-System (primary file system)

--Android-info.txt
--Clean_steps.mk
--Ramdisk.img
--System.img

--Userdata.img

--userdata-qemu.img

All dynamic libraries are stored in the obj/shared_libraries.
All static libraries are stored in the obj/static_libraries.
Several img-terminated files are target image files, where RAMDisk is the root file system image of the memory disk, SYSTEM.IMG is the primary file system image, which is a larger file, Userdata.img is a data content image. USERDATA-QEMU.IMG is a data file used by the simulator, generally not userdata.img, only-wipe-data when used to userdata.img. These image files are the files that are really needed at runtime.

Directory Analysis of Android source code PostScript

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.