Building the System 编译安卓系统

最新推荐文章于 2024-04-29 13:34:32 发布

yangjingbo111

最新推荐文章于 2024-04-29 13:34:32 发布

阅读量2.5k

点赞数

分类专栏： Android developer 官网学习笔记文章标签：安卓系统编译官方 android

Android developer 官网学习笔记专栏收录该内容

7 篇文章 0 订阅

订阅专栏

前言：

此文翻译自翻墙后的安卓官方网站，网址如下：http://source.android.com/source/building.html，可惜不少人进不去，故作此文。

正文：
原：
The following instructions to build the Android source tree apply to all branches, including master. The basic sequence of build commands is as follows:
译：
下面的编译安卓源码树的命令应用于所有分支，包括master（目前指的安卓6.0）。编译命令的基本顺序如下：

Set up environment 设置编译环境

原：
Initialize the environment with the envsetup.sh script. Note that replacing source with . (a single dot) saves a few characters, and the short form is more commonly used in documentation.
译：
使用envsetup.sh脚本初始化编译环境。可以用一个点来代替source命令，少敲几个字符（呵呵），简短的形式在文档中更常用。

$ source build/envsetup.sh

$ . build/envsetup.sh

Choose a Target 选择目标

原：
Choose which target to build with lunch. The exact configuration can be passed as an argument. For example, the following command:
译：
为lunch命令选择一个目标来编译。具体配置可以作为一个参数被传递给lunch命令。例如，下面的命令：

$ lunch aosp_arm-eng

原：
refers to a complete build for the emulator, with all debugging enabled.
译：
上面的命令指明为模拟器编译，并且使能所有的debugging 功能。

原：
If run with no arguments lunch will prompt you to choose a target from the menu.
译：
如果lunch命令后面没有参数，那么会弹出让你选择目标的菜单。

原：
All build targets take the form BUILD-BUILDTYPE, where the BUILD is a codename referring to the particular feature combination.
译：
所有的目标都采用BUILD-BUILDTYPE形式，其中BUILD 是一个指示特定特性、功能组合的代码名称。

原：
The BUILDTYPE is one of the following:
译：
BUILDTYPE 是以下其中之一:

Buildtype	Use
user	limited access; suited for production
userdebug	like “user” but with root access and debuggability; preferred for debugging
eng	development configuration with additional debugging tools

原：
For more information about building for and running on actual hardware, see Running Builds.
译：
更多关于编译和运行在实际硬件上的信息，请参见Running Builds章节。

Build the code 编译代码

（合理利用CPU资源，提高编译效率）

原：
Build everything with make. GNU make can handle parallel tasks with a -jN argument, and it’s common to use a number of tasks N that’s between 1 and 2 times the number of hardware threads on the computer being used for the build. For example, on a dual-E5520 machine (2 CPUs, 4 cores per CPU, 2 threads per core), the fastest builds are made with commands between make -j16 and make -j32.
译：
使用make命令编译一切！GUN的make命令可以通过使用一个 -jN的参数处理多个并行的任务，通常让任务数N为编译电脑CPU总线程数的1到2倍之间的数。例如：在E5520机器上（2个CPU，每个CPU有4个核，每个核2个线程），最快的编译速度应该使用make -j16 和 make -j32之间。（make -j20 或者make -j27都可以）。

$ make -j4

Run It! 运行它！

原：
You can either run your build on an emulator or flash it on a device. Please note that you have already selected your build target with lunch, and it is unlikely at best to run on a different target than it was built for.
译：
你可以将你编译好的系统运行在模拟器上或者是烧写到真实的设备中运行。请注意你已经使用lunch命令选择了编译目标，所以最好不要在编译目标之外的其他目标上运行（你懂得，按套路来）。

Flash a Device 烧写到设备

原：
To flash a device, you will need to use fastboot, which should be included in your path after a successful build. Place the device in fastboot mode either manually by holding the appropriate key combination at boot, or from the shell with
译：
为了烧写到设备上，你将需要使用fastboot工具，fastboot应该在你成功编译之后的路径中。使用手工方式在设备引导启动的时候选择合适的选项让设备进入fastboot模式，或者进入中断后敲如下命令：

$ adb reboot bootloader

原：
Once the device is in fastboot mode, run
译：
一旦设备处于fastboot模式，运行如下命令：

$ fastboot flashall -w

原：
The -w option wipes the /data partition on the device; this is useful for your first time flashing a particular device but is otherwise unnecessary.
译:
-w选项将擦除设备上的/data分区；这对你第一次烧写一个特定的设备来说是很有用的，其他情况下没必要（再擦除/data分区了）。

原：
For more information about building for and running on actual hardware, see Running Builds.
译：

Emulate an Android Device

原：
The emulator is added to your path automatically by the build process. To run the emulator, type
译：

$ emulator

Using ccache

原：
ccache is a compiler cache for C and C++ that can help make builds faster. In the root of the source tree, do the following:

译：

$ export USE_CCACHE=1
$ export CCACHE_DIR=/<path_of_your_choice>/.ccache
$ prebuilts/misc/linux-x86/ccache/ccache -M 50G

The suggested cache size is 50-100G.

On Linux, you can watch ccache being used by doing the following:

$ watch -n1 -d prebuilts/misc/linux-x86/ccache/ccache -s

On Mac OS, you should replace linux-x86 with darwin-x86.

When using Ice Cream Sandwich (4.0.x) or older, you should replace prebuilts/misc with prebuilt.

Troubleshooting Common Build Errors

Wrong Java Version

If you are attempting to build a version of Android inconsistent with your version of Java, make will abort with a message such as

************************************************************
You are attempting to build with the incorrect version
of java.

Your version is: WRONG_VERSION.
The correct version is: RIGHT_VERSION.

Please follow the machine setup instructions at
    https://source.android.com/source/download.html
************************************************************

This may be caused by:

Failing to install the correct JDK as specified in Initializing the Build Environment.
Another JDK previously installed appearing in your path. Prepend the correct JDK to the beginning of your PATH or remove the problematic JDK.
Python Version 3

Repo is built on particular functionality from Python 2.x and is unfortunately incompatible with Python 3. In order to use repo, please install Python 2.x:

$ apt-get install python

Case Insensitive Filesystem

If you are building on an HFS filesystem on Mac OS, you may encounter an error such as

************************************************************
You are building on a case-insensitive filesystem.
Please move your source tree to a case-sensitive filesystem.
************************************************************

Please follow the instructions in Initializing the Build Environment for creating a case-sensitive disk image.

No USB Permission

On most Linux systems, unprivileged users cannot access USB ports by default. If you see a permission denied error, follow the instructions Initializing the Build Environment for configuring USB access.

If adb was already running and cannot connect to the device after getting those rules set up, it can be killed with adb kill-server. That will cause adb to restart with the new configuration.