Some make commands commonly used by Android (reproduced)--good

Original URL: http://blog.sina.com.cn/s/blog_abc7e49a01011y0n.html

1.make-jxx
XX Represents the number, this command will compile the Android system and generate an image, XX represents the number of CPU cores that can be used, which is particularly useful on a configured computer, the company's 16-core Ubuntu server executes make-j16 as long as less than 20 minutes, while a dual-core PC takes 4 hours!

2. Make Snod
 This command will regenerate the mirror, consuming little time, similar toWinCE's makeimg process is useful if you modify files such as music, video, and more.

3.make CTS
This command compiles the CTS sleeve, and the compiled results are placed under the Data/app directory of the Out directory's corresponding version. Useful when CTS testing

4.make Installclean
This command clears the contents of the corresponding Board folder in the Out directory, which is equivalent to make clean, usually if you change some data files (such as remove), it is best to do the following made Installclean, otherwise the remaining in the out directory will be packaged in.

5.mm/mm-b
Development debugging most like this command, in the modified directory to execute this command, you can intelligently compile, the output of the file is pushed through the ADB to the target machine, can be easily debugged.

6.make SDK
This command generates a ready-to-publish SDK that has not yet been tried and is said to require JDK1.5

7.make Setting
can be compiled separately setting this module, has not yet tried, guess is not able to compile email, music these modules

8.make bootimage
This command can be used to generate BOOT.IMG, this image file contains the Linux Kernel,ram disk, the generated boot.img can only be burned by fastboot, which is useful when only modifying the Linux kernel

Android is more important three img files:

• Make Systemimage-system.img
• Make Userdataimage-userdata.img
• Make Ramdisk-ramdisk.img
• Make Snod-Quick pack system.img (with this command, it would build a new system.img very quickly. Well, you cannot use "Make Sno D "for all the situations. It would not check the dependences. If you change some code in the framework which would effect other applications)

Because
System.img was made from Out/target/product/xxxx/system.
If you change the contents of this folder, you want to re-produce system.img. Do not control the file dependency in the system Folde, you can use Snod this target:

• Make Snod

Definition in Build/core/makefile you can see Snod this target:
(It is stated that: Make system.img ignoring depencies)

. Phony:systemimage-nodeps Snod
Systemimage-nodeps Snod: $ (filter-out systemimage-nodeps snod,$ (makecmdgoals)) \
| $ (Internal_mkuserfs)
@echo "make [email protected]: ignoring dependencies"
$ (call build-systemimage-target,$ (Installed_systemimage))
$ (hide) $ (call assert-max-image-size,$ (Installed_systemimage), $ (board_systemimage_partition_size), yaffs)

REF:
Http://hi.baidu.com/kyan/blog/item/df7ea8d346f5c839960a163c.html
Http://r40eubuntu.blogspot.com/2010/10/systemimg.html

Some make commands commonly used by Android (reproduced)--good