android 编译 英文说明文档
2012-08-19 00:03
351 查看
http://source.android.com/source/initializing.html
Initializing the Build Environment
Downloading the Source
Building and Running
Building for Devices
Building Kernels
Known Issues
Platform Overview
Branches & Releases
Build Numbers
Life of a Patch
Submitting Patches
View Patches
Life of a Bug
Reporting Bugs
Version Control
Repo Commands
Git Resources
Using Eclipse
Code Style Guidelines
FAQs
The "Getting Started" section describes how to set up your local work environment, how to use Repo to get the Android files, and how to build the files on your machine. To build the Android source files, you will need to use Linux or Mac OS. Building under
Windows is not currently supported.
Note: The source download is approximately 8.5GB in size. You will need over 30GB free to complete a single build, and up to 100GB (or more) for a full set of builds.
For an overview of the entire code-review and code-update process, see Life of a Patch.
Some of the requirements for your build environment are determined by which version of the source code you plan to compile. See Build Numbers for a full listing of
branches you may choose from. You may also choose to download and build the latest source code (called "master"), in which case you will simply omit the branch specification when you initialize the repository.
Once you have selected a branch, follow the appropriate instructions below to set up your build environment.
These instructions apply to all branches, including master.
The Android build is routinely tested in house on recent versions of Ubuntu LTS (10.04), but most distributions should have the required build tools available. Reports of successes or failures on other distributions are welcome.
For Gingerbread (2.3.x) and newer versions, including the master branch, a 64-bit environment is required. Older versions can be compiled on 32-bit systems.
Note: It is also possible to build Android in a virtual machine. If you are running Linux in a virtual machine, you will need at least 16GB of RAM/swap and 30GB or more of disk space in order to build the Android tree.
Detailed instructions for Ubuntu and MacOS follow. In general you will need:
Python 2.5 -- 2.7, which you can download from python.org.
GNU Make 3.81 -- 3.82, which you can download from gnu.org,
JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older. You can download both from java.sun.com.
Git 1.7 or newer. You can find it at git-scm.com.
The Sun JDK is no longer in Ubuntu's main package repository. In order to download it, you need to add the appropriate repository and indicate to the system which JDK should be used.
Java 6: for Gingerbread and newer
Java 5: for Froyo and older
Note: The
You will need a 64-bit version of Ubuntu. Ubuntu 10.04 is recommended. Building using a newer version of Ubuntu is currently only experimentally supported and is not guaranteed to work on branches other than master.
On Ubuntu 10.10:
On Ubuntu 11.10:
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Under GNU/linux systems (and specifically under Ubuntu systems), regular users can't directly access USB devices by default. The system needs to be configured to allow such access.
The recommended approach is to create a file
be replaced by the actual username of the user who is authorized to access the phones over USB.
Those new rules take effect the next time a device is plugged in. It might therefore be necessary to unplug the device and plug it back into the computer.
This is known to work on both Ubuntu Hardy Heron (8.04.x LTS) and Lucid Lynx (10.04.x LTS). Other versions of Ubuntu or other variants of GNU/linux might require different configurations.
You can optionally tell the build to use the ccache compilation tool. Ccache acts as a compiler cache that can be used to speed-up rebuilds. This works very well if you do "make clean" often, or if you frequently switch between different build products.
Put the following in your .bashrc or equivalent.
By default the cache will be stored in ~/.ccache. If your home directory is on NFS or some other non-local filesystem, you will want to specify the directory in your .bashrc as well.
The suggested cache size is 50-100GB. You will need to run the following command once you have downloaded the source code.
This setting is stored in the CCACHE_DIR and is persistent.
By default, the output of each build is stored in the out/ subdirectory of the matching source tree.
On some machines with multiple storage devices, builds are faster when storing the source files and the output on separate volumes. For additional performance, the output can be stored on a filesystem optimized for speed instead of crash robustness, since all
files can be re-generated in case of filesystem corruption.
To set this up, export the
The output directory for each separate source tree will be named after the directory holding the source tree.
For instance, if you have source trees as
set to
It's important in that case to not have multiple source trees stored in directories that have the same name, as those would end up sharing an output directory, with unpredictable results.
This is only supported on Jelly Bean (4.1) and newer, including the master branch.
In a default installation, OS X runs on a case-preserving but case-insensitive filesystem. This type of filesystem is not supported by git and will cause some git commands (such as "git status") to behave abnormally. Because of this, we recommend that you always
work with the AOSP source files on a case-sensitive filesystem. This can be done fairly easily using a disk image, discussed below.
Once the proper filesystem is available, building the master branch in a modern OS X environment is very straightforward. Earlier branches, including ICS, require some additional tools and SDKs.
You can create a case-sensitive filesystem within your existing OS X environment using a disk image. To create the image, launch Disk Utility and select "New Image". A size of 25GB is the minimum to complete the build, larger numbers are more future-proof.
Using sparse images saves space while allowing to grow later as the need arises. Be sure to select "case sensitive, journaled" as the volume format.
You can also create it from a shell with the following command:
This will create a .dmg (or possibly a .dmg.sparsefile) file which, once mounted, acts as a drive with the required formatting for Android development. For a disk image named "android.dmg" stored in your home directory, you can add the following to your
mount the image when you execute "mountAndroid":
Once mounted, you'll do all your work in the "android" volume. You can eject it (unmount it) just like you would with an external drive.
To build the latest source in a Mac OS environment, you will need an Intel/x86 machine running MacOS 10.6 (Snow Leopard) or MacOS 10.7 (Lion), along with Xcode 4.2 (Apple's Developer Tools). Although Lion does not come with a JDK, it should install automatically
when you attempt to build the source.
The remaining sections for Mac OS X only apply to those who wish to build earlier branches.
To build android-4.0.x and earlier branches in a Mac OS environment, you need an Intel/x86 machine running MacOS 10.5 (Leopard) or MacOS 10.6 (Snow Leopard). You will need the MacOS 10.5 SDK.
Install Xcode from the Apple developer site. We recommend version 3.1.4 or newer, i.e. gcc 4.2. Version 4.x could cause difficulties. If you are not already registered as an Apple developer,
you will have to create an Apple ID in order to download.
Install MacPorts from macports.org.
Note: Make sure that
to your
Get make, git, and GPG packages from MacPorts:
If using Mac OS 10.4, also install bison:
For versions of Android before ICS, there is a bug in gmake 3.82 that prevents android from building. You can install version 3.81 using MacPorts by taking the following steps:
Edit
above the rsync line. Then create this directory:
In the new
Create a port index for your new local repository:
Finally, install the old version of gmake with
On MacOS the default limit on the number of simultaneous file descriptors open is too low and a highly parallel build process may exceed this limit.
To increase the cap, add the following lines to your
Your build environment is good to go! Proceed to downloading the source....
etting Started
Initializing the Build EnvironmentDownloading the Source
Building and Running
Building for Devices
Building Kernels
Known Issues
Navigating the Source
Platform OverviewBranches & Releases
Build Numbers
Contributing
Life of a PatchSubmitting Patches
View Patches
Life of a Bug
Reporting Bugs
Reference
Version ControlRepo Commands
Git Resources
Using Eclipse
Code Style Guidelines
FAQs
Initializing a Build Environment
The "Getting Started" section describes how to set up your local work environment, how to use Repo to get the Android files, and how to build the files on your machine. To build the Android source files, you will need to use Linux or Mac OS. Building underWindows is not currently supported.
Note: The source download is approximately 8.5GB in size. You will need over 30GB free to complete a single build, and up to 100GB (or more) for a full set of builds.
For an overview of the entire code-review and code-update process, see Life of a Patch.
Choosing a Branch
Some of the requirements for your build environment are determined by which version of the source code you plan to compile. See Build Numbers for a full listing ofbranches you may choose from. You may also choose to download and build the latest source code (called "master"), in which case you will simply omit the branch specification when you initialize the repository.
Once you have selected a branch, follow the appropriate instructions below to set up your build environment.
Setting up a Linux build environment
These instructions apply to all branches, including master.The Android build is routinely tested in house on recent versions of Ubuntu LTS (10.04), but most distributions should have the required build tools available. Reports of successes or failures on other distributions are welcome.
For Gingerbread (2.3.x) and newer versions, including the master branch, a 64-bit environment is required. Older versions can be compiled on 32-bit systems.
Note: It is also possible to build Android in a virtual machine. If you are running Linux in a virtual machine, you will need at least 16GB of RAM/swap and 30GB or more of disk space in order to build the Android tree.
Detailed instructions for Ubuntu and MacOS follow. In general you will need:
Python 2.5 -- 2.7, which you can download from python.org.
GNU Make 3.81 -- 3.82, which you can download from gnu.org,
JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older. You can download both from java.sun.com.
Git 1.7 or newer. You can find it at git-scm.com.
Installing the JDK
The Sun JDK is no longer in Ubuntu's main package repository. In order to download it, you need to add the appropriate repository and indicate to the system which JDK should be used.Java 6: for Gingerbread and newer
[code]$ sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner" $ sudo apt-get update $ sudo apt-get install sun-java6-jdk
Java 5: for Froyo and older
[code]$ sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu hardy main multiverse" $ sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu hardy-updates main multiverse" $ sudo apt-get update $ sudo apt-get install sun-java5-jdk
Note: The
lunchcommand in the build step will ensure that the Sun JDK is used instead of any previously installed JDK.
Installing required packages (Ubuntu 10.04 -- 11.10)
You will need a 64-bit version of Ubuntu. Ubuntu 10.04 is recommended. Building using a newer version of Ubuntu is currently only experimentally supported and is not guaranteed to work on branches other than master.[code]$ sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \ x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \ libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \ libxml2-utils xsltproc
On Ubuntu 10.10:
[code]$ sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
On Ubuntu 11.10:
[code]$ sudo apt-get install libx11-dev:i386
Installing required packages (Ubuntu 12.04)
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.[code]$ sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \ libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \ libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \ python-markdown libxml2-utils xsltproc zlib1g-dev:i386 $ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Configuring USB Access
Under GNU/linux systems (and specifically under Ubuntu systems), regular users can't directly access USB devices by default. The system needs to be configured to allow such access.The recommended approach is to create a file
/etc/udev/rules.d/51-android.rules(as the root user) and to copy the following lines in it.
<username>must
be replaced by the actual username of the user who is authorized to access the phones over USB.
[code]# adb protocol on passion (Nexus One) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>" # fastboot protocol on passion (Nexus One) SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>" # adb protocol on crespo/crespo4g (Nexus S) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>" # fastboot protocol on crespo/crespo4g (Nexus S) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>" # adb protocol on stingray/wingray (Xoom) SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>" # fastboot protocol on stingray/wingray (Xoom) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>" # adb protocol on maguro/toro (Galaxy Nexus) SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>" # fastboot protocol on maguro/toro (Galaxy Nexus) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>" # adb protocol on panda (PandaBoard) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>" # fastboot protocol on panda (PandaBoard) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>" # usbboot protocol on panda (PandaBoard) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>" # usbboot protocol on panda (PandaBoard ES) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>" # adb protocol on grouper (Nexus 7) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>" # fastboot protocol on grouper (Nexus 7) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"
Those new rules take effect the next time a device is plugged in. It might therefore be necessary to unplug the device and plug it back into the computer.
This is known to work on both Ubuntu Hardy Heron (8.04.x LTS) and Lucid Lynx (10.04.x LTS). Other versions of Ubuntu or other variants of GNU/linux might require different configurations.
Setting up ccache
You can optionally tell the build to use the ccache compilation tool. Ccache acts as a compiler cache that can be used to speed-up rebuilds. This works very well if you do "make clean" often, or if you frequently switch between different build products.Put the following in your .bashrc or equivalent.
[code]export USE_CCACHE=1
By default the cache will be stored in ~/.ccache. If your home directory is on NFS or some other non-local filesystem, you will want to specify the directory in your .bashrc as well.
[code]export CCACHE_DIR=<path-to-your-cache-directory>
The suggested cache size is 50-100GB. You will need to run the following command once you have downloaded the source code.
[code]prebuilt/linux-x86/ccache/ccache -M 50G
This setting is stored in the CCACHE_DIR and is persistent.
Using a separate output directory
By default, the output of each build is stored in the out/ subdirectory of the matching source tree.On some machines with multiple storage devices, builds are faster when storing the source files and the output on separate volumes. For additional performance, the output can be stored on a filesystem optimized for speed instead of crash robustness, since all
files can be re-generated in case of filesystem corruption.
To set this up, export the
OUT_DIR_COMMON_BASEvariable to point to the location where your output directories will be stored.
[code]export OUT_DIR_COMMON_BASE=<path-to-your-out-directory>
The output directory for each separate source tree will be named after the directory holding the source tree.
For instance, if you have source trees as
/source/master1and
/source/master2and
OUT_DIR_COMMON_BASEis
set to
/output, the output directories will be
/output/master1and
/output/master2.
It's important in that case to not have multiple source trees stored in directories that have the same name, as those would end up sharing an output directory, with unpredictable results.
This is only supported on Jelly Bean (4.1) and newer, including the master branch.
Setting up a Mac OS X build environment
In a default installation, OS X runs on a case-preserving but case-insensitive filesystem. This type of filesystem is not supported by git and will cause some git commands (such as "git status") to behave abnormally. Because of this, we recommend that you alwayswork with the AOSP source files on a case-sensitive filesystem. This can be done fairly easily using a disk image, discussed below.
Once the proper filesystem is available, building the master branch in a modern OS X environment is very straightforward. Earlier branches, including ICS, require some additional tools and SDKs.
Creating a case-sensitive disk image
You can create a case-sensitive filesystem within your existing OS X environment using a disk image. To create the image, launch Disk Utility and select "New Image". A size of 25GB is the minimum to complete the build, larger numbers are more future-proof.Using sparse images saves space while allowing to grow later as the need arises. Be sure to select "case sensitive, journaled" as the volume format.
You can also create it from a shell with the following command:
[code]# hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/android.dmg
This will create a .dmg (or possibly a .dmg.sparsefile) file which, once mounted, acts as a drive with the required formatting for Android development. For a disk image named "android.dmg" stored in your home directory, you can add the following to your
~/.bash_profileto
mount the image when you execute "mountAndroid":
[code]# mount the android file image function mountAndroid { hdiutil attach ~/android.dmg -mountpoint /Volumes/android; }
Once mounted, you'll do all your work in the "android" volume. You can eject it (unmount it) just like you would with an external drive.
Master branch
To build the latest source in a Mac OS environment, you will need an Intel/x86 machine running MacOS 10.6 (Snow Leopard) or MacOS 10.7 (Lion), along with Xcode 4.2 (Apple's Developer Tools). Although Lion does not come with a JDK, it should install automaticallywhen you attempt to build the source.
The remaining sections for Mac OS X only apply to those who wish to build earlier branches.
Branch 4.0.x and all earlier branches
To build android-4.0.x and earlier branches in a Mac OS environment, you need an Intel/x86 machine running MacOS 10.5 (Leopard) or MacOS 10.6 (Snow Leopard). You will need the MacOS 10.5 SDK.
Installing required packages
Install Xcode from the Apple developer site. We recommend version 3.1.4 or newer, i.e. gcc 4.2. Version 4.x could cause difficulties. If you are not already registered as an Apple developer,you will have to create an Apple ID in order to download.
Install MacPorts from macports.org.
Note: Make sure that
/opt/local/binappears in your path BEFORE
/usr/bin. If not, add
[code]export PATH=/opt/local/bin:$PATH
to your
~/.bash_profile.
Get make, git, and GPG packages from MacPorts:
[code]$ POSIXLY_CORRECT=1 sudo port install gmake libsdl git-core gnupg
If using Mac OS 10.4, also install bison:
[code]$ POSIXLY_CORRECT=1 sudo port install bison
Reverting from make 3.82
For versions of Android before ICS, there is a bug in gmake 3.82 that prevents android from building. You can install version 3.81 using MacPorts by taking the following steps:Edit
/opt/local/etc/macports/sources.confand add a line that says
[code]file:///Users/Shared/dports
above the rsync line. Then create this directory:
[code]$ mkdir /Users/Shared/dports
In the new
dportsdirectory, run
[code]$ svn co --revision 50980 http://svn.macports.org/repository/macports/trunk/dports/devel/gmake/ devel/gmake/
Create a port index for your new local repository:
[code]$ portindex /Users/Shared/dports
Finally, install the old version of gmake with
[code]$ sudo port install gmake @3.81
Setting a file descriptor limit
On MacOS the default limit on the number of simultaneous file descriptors open is too low and a highly parallel build process may exceed this limit.To increase the cap, add the following lines to your
~/.bash_profile:
[code]# set the number of open files to be 1024 ulimit -S -n 1024
Next: Download the source
Your build environment is good to go! Proceed to downloading the source....
相关文章推荐
- Bluetooth Low Energy for Android --- Google官方说明文档(英文)
- input输入子系统:Android-Keylayout英文说明文档
- NDK-Android.mk 英文编译说明
- 摩托罗拉三防智能DEFY ME525 官方Android 2.3升级文档、说明及教程
- android官方文档:ubuntu10.04下编译android源码之初始化编译环境 Initializing a Build Environment
- Android英文文档翻译系列(2)——HandlerThread
- mtk平台android代码编译文档
- Android Fresco图片处理库用法API英文原文文档2-2(Facebook开源Android图片库)
- 关于cocos2d-x 3.X的搭建和编译成Android平台程序的说明
- Android Fresco图片处理库用法API英文原文文档4(Facebook开源Android图片库)
- 关于Android RenderScript 的详细说明和一些实用文档
- Android编译系统(三):官方文档Android Build System
- Android英文文档翻译系列(6)——LocalBroadcastManager
- The Portable Executable File Format PE文件格式英文说明文档
- Android英文文档翻译系列(3)——AsyncTask
- 在Eclipse中用javadoc给android工程库文件生成API说明文档
- Android 编码规范说明文档
- Android Fresco图片处理库用法API英文原文文档1(Facebook开源Android图片库)
- android2.3源码下载编译全过程(附图及文档)修改版【转】
- 开源项目Universal Image Loader for Android 说明文档 (2)