Android build target list.

Document directory

• Build variants

Android build target list.

• Make SDK-build the tools that are part of an SDK (ADB, fastboot, etc .)
• Make Snod-build the system image from the current software Binaries
• Make services
• Make Runtime
• Make droid-make droid is the normal build.
• Make all-make everything, whether it is wrongly ded in the product definition or not
• Make clean-Remove all built files (prepare for a new build). Same as RM-RF out/<configuration>/
• Make modules-shows a list of submodules that can be built (list of all local_module definitions)
• Make <local_module>-make a specific module (note that this is not the same as directory name. It is the local_module definition in the Android. mk file)
• Make clean-<local_module>-clean a specific module

 

Build variants

When building for a participant product, it's often useful to have minorvariations on what is ultimately the final release build. These are thecurrently-defined build variants:

eng	This is the default flavor. A plainmakeIs the samemake eng. Installmodules tagged:eng,debug,user, And/or development. Installnon-APK modules that have no tags specified. Installapks according to the product definition files, in addition to tagged apks. ro.secure=0 ro.debuggable=1 ro.kernel.android.checkjni=1 adbIs enabled by default.
user	make user This is the flavor intended to be the final release bits. Installmodules taggeduser. Installnon-APK modules that have no tags specified. Installapks according to the product definition files; tags are ignored for APK modules. ro.secure=1 ro.debuggable=0 adbIs disabled by default.
userdebug	make userdebug The sameuser, Distinct T: Also installmodules taggeddebug. ro.debuggable=1 adbIs enabled by default.

If you build one flavor and then want to build another, you shoshould runmake installcleanBetween the two makes to guarantee thatyou don't pick up files installed by the previous flavor.
makecleanWill also suffice, but it takes a lot longer.