ubuntu 11.10下载和编译Android源码
Ubuntu下Android源码修改、编译及运行、launcher定制
环境Linux 版本：Ubuntu 11.04 （可由10.10的版本进行升级）64位系统GCC版本：gcc version 4.5.2Java版本：java version "1.6.0_26"下载android源码前注意：1、保证Ubuntu系统中的容量在80G左右，以保证足够的空间来存放android源码以及编译后的相关文件。
2、保证Ubuntu系统进行Internet访问。
联网方法：采用拨号进行连接。
相关操作步骤如下所示：1、虚拟机→设置→硬件→网络适配器→网络连接→桥接2、启动Ubuntu系统，打开终端（在普通用户下），输入相关命令如下：$ pppoeconf //打开后输入上网账号跟密码，确认保存$ sudo pon dsl-provider //上网连接命令经过这两个步骤后就可以进行上网了。
Android源码编译所依赖的tools01.$ sudo apt-get update02.$ sudo apt-get -y install git-core03.$ sudo apt-get -y install gnupg04.$ sudo apt-get -y install sun-java6-jdk flex05.$ sudo apt-get -y install bison06.$ sudo apt-get -y install gperf07.$ sudo apt-get -y install libsdl-dev08.$ sudo apt-get -y install libesd0-dev09.$ sudo apt-get -y install libwxgtk2.6-dev10.$ sudo apt-get -y install build-essential11.$ sudo apt-get -y install zip12.$ sudo apt-get -y install curl13.$ sudo apt-get -y install libncurses5-dev14.$ sudo apt-get -y install zlib1g-dev15.$ sudo apt-get -y install valgrind注意：（如果是32bit的系统的话，则要更改几个Android.mk文件）01./external/clearsilver/cgi/Android.mk02./external/clearsilver/java-jni/Android.mk03./external/clearsilver/util/Android.mk04./external/clearsilver/cs/Android.mk用gedit打开，修改m64为m32即可另外将build/core/main.mk中的ifneq (64,$(findstring 64,$(build_arch)))修改为：ifneq (i686,$(findstring i686,$(build_arch)))对于32位系统所出现的问题，解决方法：Error1：make: ***[out/host/linux-x86/obj/STATIC_LIBRARIES/libutils_intermediates/RefBase.o] error 1在terminal中输入$ gedit frameworks/base/libs/utils/Android.mk将LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS)修改为：LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS) –fpermissiveError2：make: *** [out/host/linux-x86/obj/EXECUTABLES/obbtool_intermediates/Main.o] error 1此处编译错误是由于ubuntu 11.10采用了GCC4.6.1导致的修改源码目录下/build/core/combo/HOST_linux-x86.mk并将以下语句：HOST_GLOBAL_CFLAGS+= -D_FORTIFY_SOURCE=0修改为：HOST_GLOBAL_CFLAGS+= -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0Android源码下载1、安装repo安装过程步骤如下所示：Repo下载安装1、$ mkdir ~/bin //在home目录下创建bin文件夹2、$ PATH=~/bin:$PA TH //环境变量设置3、$ curl https:///dl/googlesource/git-repo/repo > ~/bin/repo //repo下载4、$ chmod a+x ~/bin/repo //权限设置，保证repo可执行Repo client初始化1、$ mkdir Android //创建Android目录，用于存放下载的android源码2、$ cd Android //进入到Android目录3、$ repo init -u https:///platform/manifest //指定URL清单,指定包含在Android源代码的各种存储库将被安置在工作目录中当然也可以指定android版本，使用如下命令：$ repo init -u https:///platform/manifest -b android-4.0.1_r1Android源码文件获取$ repo sync注意：在Android源码下载过程中凡出现问题，可以进入Android源码下载的相关官方网站/source/downloading.html 进行查看。
在Ubuntu上下载、编译和安装Android最新源代码
在Ubuntu上下载、编译和安装Android最新源代码在Ubuntu上下载、编译和安装Android最新源代码官⽹内容：Initializing a Build EnvironmentThe "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 undernot currently supported.Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (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.Setting up a Linux build environmentThe 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.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.In general you will need:Python 2.4 -- 2.7, which you can download from .JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older. You can download both from .Git 1.7 or newer. You can find it at .Detailed instructions for Ubuntu 10.04+ follow.Installing the JDKThe 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$ sudo add-apt-repository "deb / lucid partner"$ sudo apt-get update$ sudo apt-get install sun-java6-jdkJava 5: for Froyo and older$ sudo add-apt-repository "deb /ubuntu hardy main multiverse"$ sudo add-apt-repository "deb /ubuntu hardy-updates main multiverse"$ sudo apt-get update$ sudo apt-get install sun-java5-jdkInstalling required packages64-bit (recommended)$ 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 libxm On newer versions of Ubuntu such as 11.10 you may need to do the following:$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so32-bit (experimental)$ sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown libxml2-utilsConfiguring USB AccessUnder 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.must be replaced by the actual username of the user who is authorized to access the phones over USB.# 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 maguro (Galaxy Nexus)SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"# fastboot protocol on maguro (Galaxy Nexus)SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", 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 a Mac OS X build environmentTo build the Android files in a Mac OS environment, you need an Intel/x86 machine running MacOS 10.6 (Snow Leopard).Android must be built on a case-sensitive file system because the sources contain files that differ only in case. We recommend that you build Android on a partition that has been formatted with the journaled file system HFS+. HFS+ is required to successfully OS applications such as the Android Emulator for OS X.Creating a case sensitive disk imageIf you want to avoid partitioning/formatting your hard drive, you can use a case-sensitive disk image instead. 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-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:# hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/android.dmgThis 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 toyour ~/.bash_profile to mount the image when you execute "mountAndroid":# mount the android file imagefunction 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.Installing required packagesInstall 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 .Note: Make sure that /opt/local/bin appears in your path BEFORE /usr/bin. If not, addexport PATH=/opt/local/bin:$PATHto your ~/.bash_profile.Get make, git, and GPG packages from MacPorts:$ POSIXLY_CORRECT=1 sudo port install gmake libsdl git-core gnupgIf using Mac OS 10.4, also install bison:$ POSIXLY_CORRECT=1 sudo port install bisonReverting from make 3.82There 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.conf and add a line that saysfile:///Users/Shared/dportsabove the rsync line. Then create this directory:$ mkdir /Users/Shared/dportsIn the new dports directory, run$ svn co --revision 50980 /repository/macports/trunk/dports/devel/gmake/ devel/gmake/Create a port index for your new local repository:$ portindex /Users/Shared/dportsFinally, install the old version of gmake with$*************************Setting a file descriptor limitOn 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:# set the number of open files to be 1024ulimit -S -n 1024Downloading the Source TreeInstalling RepoRepo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see Version Control.To install, initialize, and configure Repo, follow these steps:Make sure you have a bin/ directory in your home directory, and that it is included in your path:$ mkdir ~/bin$ PATH=~/bin:$PATHDownload the Repo script and ensure it is executable:$ curl https:///dl/googlesource/git-repo/repo > ~/bin/repo$ chmod a+x ~/bin/repoThe SHA-1 checksum for repo is e1fd3bef059d152edf4d0522590725d317bc637fInitializing a Repo clientAfter installing Repo, set up your client to access the android source repository:Create an empty directory to hold your working files. If you're using MacOS, this has to be on a case-sensitive filesystem. Give it any name you like:$ mkdir WORKING_DIRECTORY$ cd WORKING_DIRECTORYRun repo init to bring down the latest version of Repo with all its most recent bug fixes. You must specify a URL for the manifest, which specifies where the various repositories included in the Android source will be placed within your working directory.$ repo init -u https:///platform/manifestTo check out a branch other than "master", specify it with -b:$ repo init -u https:///platform/manifest -b android-4.0.1_r1When prompted, please configure Repo with your real name and email address. To use the Gerrit code-review tool, you will need an email address that is connected with a registered Google account. Make sure this is a live address at which you can receive mes The name that you provide here will show up in attributions for your code submissions.A successful initialization will end with a message stating that Repo is initialized in your working directory. Your client directory should now contain a .repo directory where files such as the manifest will be kept.Getting the filesTo pull down files to your working directory from the repositories as specified in the default manifest, run$ repo syncThe Android source files will be located in your working directory under their project names. The initial sync operation will take an hour or more to complete. For more about repo sync and other Repo commands, see Version Control.Verifying Git TagsLoad the following public key into your GnuPG key database. The key is used to sign annotated tags that represent releases.$ gpg --importCopy and paste the key(s) below, then enter EOF (Ctrl-D) to end the input and process the keys.-----BEGIN PGP PUBLIC KEY BLOCK-----Version: GnuPG v1.4.2.2 (GNU/Linux)mQGiBEnnWD4RBACt9/h4v9xnnGDou13y3dvOx6/t43LPPIxeJ8eX9WB+8LLuROSVlFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw7lFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw78tR1cXb197Ob8kOfQB3A9yk2XZ4ei4ZC3i6wVdqHLRxABdncwu5hOF9KXwCgkxMDu4PVgChaAJzTYJ1EG+UYBIUEAJmfearb0qRAN7dEoff0FeXsEaUA6U90sEoVks0ZwNj96SA8BL+a1OoEUUfpMhiHyLuQSftxisJxTh+2QclzDviDyaTrkANjdYY7p2cq/HMdOY7LJlHaqtXmZxXjjtw5Uc2QG8UY8aziU3IE9nTjSwCXeJnuyvoizl9/I1S5jU5SA/9WwIps4SC84ielIXiGWEqq6i6/sk4I9q1YemZF2XVVKnmI1F4iCMtNKsR4MGSa1gA8s4iQbsKNWPgp7M3a51JCVCu6l/8zTpA+uUGapw4tWCp4o0dpIvDPBEa9b/aF/ygcR8mh5hgUfpF9IpXdknOsbKCvM9lSSfRciETykZc4wrRCVGhlIEFuZHJvaWQgT3BlbiBTb3VyY2UgUHJvamVjdCA8aW5pdGlhbC1jb250cmlidXRpb25AYW5kcm9pZC5jb20+iGAEExECACAFAknnWD4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDorT+BmrEOeNr+AJ42Xy6tEW7r3KzrJxnRX8mij9z8tgCdFfQYiHpYngkI2t09Ed+9Bm4gmEO5Ag0ESedYRBAIAKVW1JcMBWvV/0Bo9WiByJ9WJ5swMN36/vAlQN4mWRhfzDOk/Rosdb0csAO/l8Kz0gKQPOfObtyYjvI8JMC3rmi+LIvSUT9806UphisyEmmHv6U8gUb/xHLIanXGxwhYzjgeuAXVCsv+EvoPIHbY4L/KvP5x+oCJIDbkC2b1TvVk9PryzmE4BPIQL/NtgR1oLWm/uWR9zRUFtBnE411aMAN3qnAHBBMZzKMXLWBGWE0znfRrnczI5p49i2YZJAjyX1P2WzmScK49CV82dzLo71MnrF6fj+Udtb5+OgTg7Cow+8PRaTkJEW5Y2JIZpnRUq0CYxAmHYX79EMKHDSThf/8AAwUIAJPWsB/MpK+KMs/s3r6nJrnYLTfdZhtmQXimpoDMJg1zxmL8UfNUKiQZ6esoAWtDgpqt7Y7sKZ8laHRARonte394hidZzM5nb6hQvpPjt2OlPRsyqVxw4c/KsjADtAuKW9/d8phbN8bTyOJo856qg4oOEzKG9eeF7oaZTYBy33BTL0408sEBxiMior6b8LrZrAhkqDjAvUXRwm/fFKgpsOysxC6xi553CxBUCH2omNV6Ka1LNMwzSp9ILz8jEGqmUtkBszwoG1S8fXgE0Lq3cdDM/GJ4QXP/p6LiwNF99faDMTV3+2SAOGvytOX6KjKVzKOSsfJQhN0DlsIw8hqJc0WISQQYEQIACQUCSedYRAIbDAAKCRDorT+BmrEOeCUOAJ9qmR0lEXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM==Wi5D-----END PGP PUBLIC KEY BLOCK-----After importing the keys, you can verify any tag with$ git tag -v TAG_NAMEBuilding the SystemThe basic sequence of build commands is as follows:InitializeInitialize 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.$ source build/envsetup.shor$ . build/envsetup.shChoose a TargetChoose which target to build with lunch. The exact configuration can be passed as an argument, e.g.$ lunch full-engThe example above refers to a complete build for the emulator, with all debugging enabled.If run with no arguments lunch will prompt you to choose a target from the menu.All build targets take the form BUILD-BUILDTYPE, where the BUILD is a codename referring to the particular feature combination:Build name Device Notesfull emulator fully configured with all languages, apps, input methodsfull_maguro maguro full build running on Galaxy Nexus GSM/HSPA+ ("maguro")full_panda panda full build running on PandaBoard ("panda")and the BUILDTYPE is one of the following:Buildtype Useuser limited access; suited for productionuserdebug like "user" but with root access and debuggability; preferred for debuggingeng development configuration with additional debugging toolsFor more information about building for and running on actual hardware, see Building for devicesBuild the CodeBuild 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. E.g. on a dual-E5520 mac CPUs, 4 cores per CPU, 2 threads per core), the fastest builds are made with commands between make -j16 and make -j32.$ make -j4Run 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.Flash a DeviceTo 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$ adb reboot bootloaderOnce the device is in fastboot mode, run$ fastboot flashall -wThe -w option wipes the /data partition on the device; this is useful for your first time flashing a particular device, but is otherwise unnecessary.For more information about building for and running on actual hardware, see Building for devicesEmulate an Android DeviceThe emulator is added to your path automatically by the build process. To run the emulator, type$ emulatorUsing ccacheccache 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$ prebuilt/linux-x86/ccache/ccache -M 20GYou can watch ccache being used by doing the following:$ watch -n1 -d prebuilt/linux-x86/ccache/ccache -sOn OSX, you should replace linux-x86 with darwin-x86.Troubleshooting Common Build ErrorsWrong Java VersionIf you are attempting to build froyo or earlier with Java 1.6, or gingerbread or later with Java 1.5, make will abort with a message such as************************************************************You are attempting to build with the incorrect versionof java.Your version is: WRONG_VERSION.The correct version is: RIGHT_VERSION.Please follow the machine setup instructions at/download************************************************************This may be caused byfailing to install the correct JDK as specified on the Initializing page. Building Android requires Sun JDK 5 or 6 depending on which release you are building.another JDK that you previously installed appearing in your path. You can remove the offending JDK from your path with:$ export PATH=${PATH/\/path\/to\/jdk\/dir:/}Python Version 3Repo 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 pythonGmake Version 3.82There is a bug in make version 3.82 on Mac OS that prevents building Android.TODO: what the error looks like with GNU make 3.82 on older builds that don't explicitly detect it.Follow the instructions on the Initializing page for reverting GNU make from 3.82 to 3.81.Case Insensitive FilesystemIf you are building on an HFS filesystem on Mac OS X, 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 on the Initializing page for creating a case-sensitive disk image.No USB PermissionOn most Linux systems, unprivileged users cannot access USB ports by default. If you see a permission denied error, follow the instructions on the Initializing page 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.Building for devicesThis page complements the main page about Building with information that is specific to individual devices.The only supported phone with the current release is the GSM/HSPA+ Galaxy Nexus, a.k.a. "maguro". GSM/HSPA+ Galaxy Nexus is currently the recommended device to use with the Android Open-Source Project.In addition, PandaBoard a.k.a. "panda" is supported in the master branch only, but is currently considered experimental. The specific details to use a PandaBoard with the Android Open-Source Project are in the file device/ti/panda/README in the source tree. Nexus S, a.k.a. "crespo", and Nexus S 4G, a.k.a. "crespo4g", are supported with gingerbread, but can't currently be used with newer versions of the Android Open-Source Project.Nexus One a.k.a. "passion" is obsolete, was experimental in gingerbread and unsupported, and can't be used with newer versions of the Android Open-Source Project.Android Developer Phones (ADP1 and ADP2, a.k.a. "dream" and "sapphire") are obsolete, were experimental and unsupported in froyo, and can't be used with newer versions of the Android Open-Source Project.Building fastboot and adbIf you don't already have those tools, fastboot and adb can be built with the regular build system. Follow the instructions on the page about building, and replace the main make command with$ make fastboot adbBooting into fastboot modeDuring a cold boot, the following key combinations can be used to boot into fastboot mode, which is a mode in the bootloader that can be used to flash the devices:Device Keysmaguro Press and hold both Volume Up and Volume Down, then press and hold Powercrespo Press and hold Volume Up, then press and hold Powercrespo4g Press and hold Volume Up, then press and hold Powerpassion Press and hold the trackball, then press Powersapphire Press and hold Back, then press Powerdream Press and hold Back, then press PowerAlso, on devices running froyo or later where adb is enabled, the command adb reboot bootloader can be used to reboot from Android directly into the bootloader with no key combinations.Unlocking the bootloaderIt's only possible to flash a custom system if the bootloader allows it.This is the default setup on ADP1 and ADP2.On Nexus One, Nexus S, Nexus S 4G, and Galaxy Nexus, the bootloader is locked by default. With the device in fastboot mode, the bootloader is unlocked with$ fastboot oem unlockThe procedure must be confirmed on-screen, and deletes the user data for privacy reasons. It only needs to be run once.On Nexus One, the operation voids the warranty and is irreversible.On Nexus S, Nexus S 4G, and Galaxy Nexus, the bootloader can be locked back with$ fastboot oem lockObtaining proprietary binariesStarting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.Official binaries for Nexus S, Nexus S 4G, Galaxy Nexus, and PandaBoard can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.There are no official binaries for Nexus One, ADP2 or ADP1.Extracting the proprietary binariesEach set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.There's an additional step on Nexus S 4G. Build the signapk tool with$ make signapkThen reassemble the proprietary applicatons with$ vendor/samsung/crespo4g/reassemble-apks.shCleaning up when adding proprietary binariesIn order to make sure that the newly installed binaries are properly taken into account after being extracted, the existing output of any previous build needs to be deleted with$ make clobberPicking and building the configuration that matches a deviceThe steps to configure and build the Android Open-Source Project are described in the page about Building.The recommended builds for the various devices are available through the lunch menu, accessed when running the lunch command with no arguments:Device Branch Build configurationmaguro android-4.0.1_r1full_maguro-userdebugpanda master full_panda-engcrespo android-2.3.6_r1full_crespo-userdebugcrespo4g android-2.3.7_r1full_crespo4g-userdebugpassion android-2.3.6_r1full_passion-userdebugsapphire android-2.2.2_r1full_sapphire-userdebugdream android-2.2.2_r1full_dream-userdebugFlashing a deviceSet the device in fastboot mode if necessary (see above).Because user data is typically incompatible between builds of Android, it's typically better to delete it when flashing a new system.$ fastboot erase cache$ fastboot erase userdataAn entire Android system can be flashed in a single command: this writes the boot, recovery and system partitions together after verifying that the system being flashed is compatible with the installed bootloader and radio, and reboots the system.$ fastboot flashallOn maguro, panda, crespo, crespo4g, sapphire and dream (but not on passion), the commands above can be replaced with a single command$ fastboot -w flashallNexus S, Nexus S 4G and Galaxy Nexus Bootloader and Cell Radio compatibilityOn Nexus S, Nexus S 4G, and Galaxy Nexus, each version of Android has only been thoroughly tested with on specific version of the underlying bootloader and cell radio software. However, no compatibility issues are expected when running newer systems with bootloaders and radio images according to the following tables.Nexus S (worldwide version "XX"):Android Version Preferred Bootloader Preferred Radio Also possible2.3 (GRH55)I9020XXJK1I9020XXJK82.3.1 (GRH78)I9020XXJK1I9020XXJK82.3.2 (GRH78C)I9020XXJK1I9020XXJK82.3.3 (GRI40)I9020XXKA3I9020XXKB1All previous versions2.3.4 (GRJ22)I9020XXKA3I9020XXKD1All previous versions2.3.5 (GRJ90)I9020XXKA3I9020XXKF1All previous versions2.3.6 (GRK39F)I9020XXKA3I9020XXKF1All previous versionsNexus S (850MHz version "UC"):Android Version Preferred Bootloader Preferred Radio Also possible2.3.3 (GRI54)I9020XXKA3I9020UCKB22.3.4 (GRJ22)I9020XXKA3I9020UCKD1All previous versions2.3.5 (GRJ90)I9020XXKA3I9020UCKF1All previous versions2.3.6 (GRK39C)I9020XXKA3I9020UCKF1All previous versions2.3.6 (GRK39F)I9020XXKA3I9020UCKF1All previous versionsNexus S (Korea version "KR"):Android Version Preferred Bootloader Preferred Radio Also possible2.3.3 (GRI54)I9020XXKA3I9020KRKB32.3.4 (GRJ22)I9020XXKA3M200KRKC1All previous versions2.3.5 (GRJ90)I9020XXKA3M200KRKC1All previous versions2.3.5 (GRJ90)I9020XXKA3M200KRKC1All previous versionsAndroid Version Preferred Bootloader Preferred Radio Also possible2.3.6 (GRK39F)I9020XXKA3M200KRKC1All previous versionsNexus S 4G:Android Version Preferred Bootloader Preferred Radio Also possible2.3.4 (GRJ06D)D720SPRKC5D720SPRKC92.3.4 (GRJ22)D720SPRKC5D720SPRKD8All previous versions2.3.5 (GRJ90)D720SPRKC5D720SPRKE5All previous versions2.3.7 (GWK74)D720SPRKE1D720SPRKH1 (*)All previous versionsGalaxy Nexus (GSM/HSPA+):Android Version Preferred Bootloader Preferred Radio Also possible4.0.1 (ITL41D)PRIMEKJ10I9250XXKK1If you're building a new version of Android, if your Nexus S, Nexus S 4G or Galaxy Nexus has an older bootloader and radio image that is marked as being also possible in the table above but is not recognized by fastboot, you can locally delete the bootloader and version-baseband lines in device/samsung/crespo/board-info.txt or device/samsung/crespo4g/board-info.txt ordevice/samsung/maguro/board-info.txt(*) As a note, radio version D720SPRKH1 for Nexus S 4G sometimes erroneously reports version D720SPRKE1. If this is the case for your Nexus S 4G, you can locally modify the version-baseband line in device/samsung/crespo4g/board-info.txt accordingly.⼀. 环境准备。
Ubuntu下编译Android源码并运行Emulator 2
Ubuntu下编译Android源码并运行Emulator 2//apt-get autoremove sun-java5-jdk//apt-get install nautilus-open-terminalandroid源码的编译安装虚拟机时建议设置空间为16G左右，否则后面编译源代码可能会导致空间不够编译环境：Ubuntu8.101、安装一些环境sudo apt-get install build-essential //sudo apt-get install makesudo apt-get install gccsudo apt-get install g++ //sudo apt-get install libc6-devsudo apt-get install patch //sudo apt-get install texinfo //sudo apt-get install libncurses-dev //sudo apt-get install git-core gnupg //sudo apt-get install flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl sudo apt-get install ncurses-devsudo apt-get install zlib1g-devsudo apt-get install valgrindsudo apt-get install python2.5安装java环境sudo apt-get install sun-java5-jdk不要用sun-java6-jdk，否则会有问题2、设置环境变量vim ~/.bashrc在.bashrc中新增或整合PA TH变量，如下#java 程序开发/运行的一些环境变量在home/你的用户名/.bashrc中加入下面一些，有些是后面运行编译后的模拟器而用的export JA VA_HOME=usr/lib/jvm/java-1.5.0-sunexport JRE_HOME=usr/lib/jvm/java-1.5.0-sun/jreexport PA TH=$PATH JA V A_HOME/binexport PA TH=$PATH:~/mydroid/out/host/linux-x86/binexport ANDROID_PRODUCT_OUT=~/mydroid/out/target/product/genericexport CLASSPATH=.{JA V A_HOME}/lib JRE_HOME/lib CLASSPATHexport JA VA_PATH=${JA V A_HOME}/bin{JRE_HOME}/binHOME_BIN=~/bin/export PA TH=${PATH}{JA V A_PA TH}{JRE_PATH}{HOME_BIN};3、安装repo（用来更新android源码）创建~/bin目录，用来存放repo程序，如下：$ cd ~$ mkdir bin注意：下载后的.repo也许并不在这个文件夹中，请返回上一级目录找到后拷贝至此下载repo脚本并使其可执行：$ curl /repo >~/bin/repo$ chmod a+x ~/bin/repo4、下载android源码并更新之$ mkdir mydroid$ cd mydroid方式一建议不要用repo来下载（android源码超过1G，非常慢），直接在网上下载http: ///bbs/pub/cupcake.tar.gz。
Android源代码下载步骤(WINDOWS系统)
Android全工程源代码下载步骤详解(WINDOWS系统)统一通知平台：陈建波由于android代码量庞大，建议在win系统下用SourceInsight查看，所有只提供了win系统下的详细下载方式1、安装GIT工具,安装python工具Python工具一定要使用目录中的python-2.7.12.amd64.msi版本，脚本getGitRepos.py是基于python-2.7.12编写，其他版本在编解码字符时候会出现异常如果电脑上已经下载了其他版本python，不需要卸载，只需要安装python-2.7.12，然后将原配置的python环境变量修改为python-2.7.12环境配置即可2、配置Git环境变量，配置python环境变量运行git--version出现下面输出表明环境变量配置成功运行python出现下面输出表明环境变量配置成功3、双击win目录下cloneRepos.sh在当前目录下会生成五个html文件，这五个文件抓取了github下Android仓库URL4、创建源代码下载命令执行python getGitRepos.py < .1.html该命令的输出为：新建文件gitRepos.sh并将上图白色部分拷贝到gitRepos.sh依次执行python getGitRepos.py < .1.htmlpython getGitRepos.py < .2.htmlpython getGitRepos.py < .3.htmlpython getGitRepos.py < .4.htmlpython getGitRepos.py < .5.html并将输出全部拷贝到gitRepos.sh5、将脚本gitRepos.sh放入到一个足够大的磁盘中(Android源代码非常庞大，超过10G)双击gitRepos.sh，代码开始下载了，由于Android代码量巨大，请保持足够的带宽和耐心，预计下载时间超过三小时OK，全部搞定，收工。
Ubuntu 11.10 图形(图解)安装教程、基本设置、网络设置、软件源、硬件驱动、Unity 3D、Gnome3、U盘安装
Ubuntu 11.10 （Oneiric Ocelot ）图形（图解）安装教程、基本设置、网络设置、软件源、语言与输入法、硬件驱动、Unity 3D、Gnome3、Ubuntu文档、制作USB Live、U盘安装、软件安装、简介目录一．准备安装Ubuntu11.10系统1.1 Ubuntu简介1.1.1 Ubuntu正式支援的衍生版本包括1.1.2 介绍Ubuntu 11.10以下特点1.1.3 Ubuntu的正式发音1.1.4 官方网站与文档1.2 获得Ubuntu发行版1.2.1 从镜像站点上下载ISO的镜像文件1.2.2 将ISO镜像文件制作成CD/DVD1.3 硬盘分区方案二．光盘安装Ubuntu 11.102.1 语言2.2 确认安装条件2.3 分区硬盘及格式化硬盘2.3.1 Ubuntu 安裝程序提供了几个方案2.3.2 其他选项 (Something else)（手动分区：/、swap、/home）2.4 所在地区和国家2.5 键盘类型2.6 使用者资料及密码2.7 完成安装2.8 初次开机三．安装后系统设置3.1 设置网络3.1.1 有线网络3.1.2 无线网络3.1.3 拨号上网（PPPOE）3.2 设置软件源与升级3.3 安装语言套件 (Language Pack)3.4 输入法3.5 修正时区及时间3.6 硬件驱动3.7 Unity 3D3.8 Gnome33.9 窗口按钮改为右手（使用于Unity桌面）四．安装软件4.1 安装压缩工具4.2 flash插件4.3 Google Chrome浏览器4.4 QQ4.5 msn4.6 pdf4.7 运行Windows软件4.8 安装 rpm 软件包4.9 支持DVD播放4.10 Ubuntu下安装显卡驱动4.10.1 Nvidia显卡驱动的安装4.10.2 ATI显卡驱动的安装五．U盘安装Ubuntu 11.105.1 Windows5.2 Linux Ubuntu一．准备安装Ubuntu 11.10系统1．Ubuntu简介Ubuntu是一个以桌面应用为主的Linux操作系统，其名称来自非洲南部祖鲁语或豪萨语的“ubuntu”一词（译为吾帮托或乌班图），意思是“人性”、“我的存在是因为大家的存在”，是非洲传统的一种价值观，类似华人社会的“仁爱”思想。
ubuntu下编译android源码错误解决记录
数据库系统管理制度数据库系统管理制度是指为了保障数据库系统的安全、稳定和高效运行，而制定的一系列规章制度和管理措施。
合理的数据库系统管理制度可以提高数据库系统的可靠性，保护数据的安全性，防止数据丢失和泄露，提高数据的完整性、一致性和可用性。
以下是数据库系统管理制度的一些要点：一、数据库系统管理的基本原则1.安全原则：确保数据库系统的安全，防止数据被非法拷贝、篡改或泄露。
2.稳定原则：保证数据库系统的稳定运行，防止系统故障和服务中断。
3.效率原则：提高数据库系统的运行效率，保证用户可以快速访问和处理数据。
4.合规原则：遵守相关法律法规和企业规定，保护用户隐私和敏感数据。
二、数据库系统管理的组织机构和职责1.数据库管理员（DBA）的职责：负责数据库系统的安装、配置、备份和恢复，监控系统性能，并对系统进行优化，管理用户的账号和权限，解决数据库系统相关的问题。
2.安全管理员的职责：负责数据库系统的安全策略和控制策略的制定和执行，制定用户权限管理规则，监控和审计数据库系统的访问和活动，检查和处理安全漏洞。
3.运维人员的职责：负责日常维护工作，包括系统巡检、性能监控、问题排查和解决，数据库备份和恢复等。
三、数据库系统管理的技术标准和流程1.数据库系统的选择和部署标准：根据业务需求和安全要求，选择合适的数据库系统，并根据标准化的部署流程进行安装和配置。
2.数据库系统的备份和恢复标准：制定定期备份数据库和日志的策略，保证数据不丢失，同时确保备份的可靠性和完整性。
3.数据库系统的安全管理标准：建立用户权限管理体系，对数据库用户进行分类和授权，限制用户的访问权限，定期修改密码，确保数据库系统的安全性。
4.数据库系统的性能管理标准：监控数据库系统的性能指标，定期进行性能优化，包括索引优化、SQL语句优化、硬件升级等，提高数据库系统的响应速度和并发能力。
5.数据库系统的故障处理标准：建立故障处理流程，监控系统运行状态，及时发现和解决故障，确保系统可用性。
在Ubuntu上下载、编译和安装Android最新内核源代码(Linux Kernel)
在前一篇文章提到，从源代码树下载下来的最新Android源代码，是不包括内核代码的，也就是Android源代码工程默认不包含Linux Kernel代码，而是使用预先编译好的内核，也就是prebuilt/android-arm/kernel/kernel-qemu文件。
那么，如何才能DIY自己的内核呢？这篇文章一一道来。
一. 首选，参照前一篇在Ubuntu上下载、编译和安装Android最新源代码准备好Android源代码目录。
二. 下载Linux Kernel for Android源代码。
1. 使用GIT工具下载，执行以下命令：USER-NAME@MACHINE-NAME:~/Android$ mkdir kernelUSER-NAME@MACHINE-NAME:~/Android$ cd kernelUSER-NAME@MACHINE-NAME:~/Android/kernel$ git clonegit:///kernel/common.git同样是经过漫长的等待后，在kernel目录下有一个common目录，Linux内核代码就在这里了。
2. 下载完成后，可以查看下载的内核代码版本：USER-NAME@MACHINE-NAME:~/Android/kernel$ cd commonUSER-NAME@MACHINE-NAME:~/Android/kernel/common$ git branch android-2.6.363. 下载完Android的Linux内核代码后，会发现在arch/arm/configs下没有模拟器要使用的硬件配置文件goldfish_defconfig，而这个配置文件是编译内核代码时需要用到的，因此，需要checkout goldfish版本：USER-NAME@MACHINE-NAME:~/Android/kernel/common$ git branch -a * android-2.6.36remotes/origin/HEAD -> origin/android-2.6.36remotes/origin/android-2.6.35remotes/origin/android-2.6.36remotes/origin/archive/android-2.6.25remotes/origin/archive/android-2.6.27remotes/origin/archive/android-2.6.29remotes/origin/archive/android-2.6.32remotes/origin/archive/android-gldfish-2.6.29remotes/origin/archive/android-goldfish-2.6.27选择android-gldfish-2.6.29：USER-NAME@MACHINE-NAME:~/Android/kernel/common$ git checkoutremotes/origin/archive/android-gldfish-2.6.29下载完毕后，就能在arch/arm/configs下看到goldfish_defconfig这个文件了。
Ubuntu下编译Android源码全过程
Ubuntu下编译Android源码全过程（转）源码, 编译, Ubuntu, Android一、获取Android源代码Git是LinuxTorvalds（Linux之父）为了帮助管理Linux内核开发而开发的一个开放源码的分布式版本控制软件，它不同于Subversion、CVS这样的集中式版本控制系统。
在集中式版本控制系统中只有一个仓库（Repository），许多个工作目录（WorkingCopy），而在Git这样的分布式版本控制系统中（其他主要的分布式版本控制系统还有BitKeeper、Mercurial、GNUArch、Bazaar、Darcs、SVK、Monotone等），每一个工作目录都包含一个完整仓库，它们支持离线工作，本地提交可以稍后提交到服务器上。
因为Android是由Kernel、Dalvik、Bionic、Prebuilt、build等多个项目组成，如果我们分别使用Git来逐个获取显得很麻烦，所以Android项目编写了一个名为Repo的Python 的脚本来统一管理这些项目的仓库，使得项目的获取更加简单。
在Ubuntu 8.04上安装Git只需要设定正确的更新源，然后使用apt-get就可以了，apt-get 是一条Linux命令，主要用于自动从互联网的软件仓库中搜索、安装、升级、卸载软件或操作系统。
apt-get命令一般需要root权限执行，所以一般跟着sudo命令。
sudo apt-get install git-core curl这条命令会从互联网的软件仓库中安装git-core和curl。
其中curl是一个利用URL语法在命令行方式下工作的文件传输工具，它支持很多协议，包括FTP、FTPS、HTTP、HTTPS、TELENT等，我们需要安装它从网络上获取Repo脚本文件。
curl/repo>~/bin/repo这句命令会下载repo脚本文件到当前主目录的/bin目录下，并保存在文件repo中。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
ubuntu 11.10下载和编译Android源码2012-03-04 21:52:52标签：下载编译源码android原创作品，允许转载，转载时请务必以超链接形式标明文章原始出处、作者信息和本声明。
否则将追究法律责任。
/4350852/796090ubuntu 11.10下载和编译Android源码由衷感谢网上的各个博主的文章，给了小弟我莫大的帮助。
这里呢，小弟也把自己的经历记录下来，以供大家参考^^。
这篇应该算是零基础、从无到有的流程介绍了。
由于是事后写这篇文章，算是总结吧，可能会遗漏一些东西，但我会尽力写清楚的！一、安装ubuntu 11.10官方很照顾我们啊，还专门有中文的下载链接，而且在“4）安装程序”内将步骤也阐述的非常清晰明了，照着做就行了。
官方网址（下载&安装）：/download/ubuntu/download-zh1）我的ubuntu单系统，总320G，分区：/，50G；swap，1G？；/home：其余。
1、swap不记得是1G还是2G了，多方资料查说不建议超过2G，总之我是照办了。
更权威点的是：if (M<2) S=M*2 else S=M+2。
M->RAM、S->swap。
（执行sudo fdisk –l查了分区，那串数字是位数么T^T）2、至于分区时这些挂载点的意义，只需Google下“Linux 挂载点”就成。
更多有关ubuntu的东西，可以去ubuntu中文找找（/及其Wiki标签）。
2）快捷操作1、复制&粘贴（最快捷的）：鼠标左键选中即复制，鼠标中间按下去即粘贴。
2、Alt+F10：窗口最大化；Alt+F5：窗口恢复；Alt+F9：窗口最小化；更多：系统设置->键盘->快捷键。
3、Ctrl+Alt+T：打开终端（这个最重要了）3）shell命令注意$前~表示用户目录开始（即/home/<user name>），而/是系统目录开始。
执行pwd可查看当前工作目录。
还有Tab键自动补全路径，上下方向浏览之前的命令等。
和windows下类似，这些都能加快我的效率。
（有点废话==）具体步骤内shell命令的作用都会简单注明，更多请参见附件《Linux命令大全(修改版).chm》^^。
二、SDK集成开发环境搭建过程和Windows下类似。
注意：Eclispe最好从官网下载，不要用下载中心的，需要添加Eclispe版本更新源什么的。
（我一开始是用应用中心下载的Eclispe，一些问题也解决了，但更新下载时在某处卡住，试了多次后，流泪奔向了官方的怀抱T^T）需要搭建的请挪至：/taskiller/blog/38849?catalog=136911。
三、Android源码下载我下载和编译的是2.3.3_r1和4.0.3_r1两个版本的源码。
之前有弄2.2的，但是一直下载不下来，伤心T^T（关了部分服务器的原因么？）。
补充一点：2.2及之前的需要JDK5。
1）更新ubuntu源为网易源为了下载速度，更新下比较好，至少也可以心里安慰下自己吗。
（虽然我是后来更新的，但没比较前后效果==）1、sudo –s（superuser do，提至root权限，exit退出）2、cp /etc/apt/sources.list /etc/apt/sources.list.bak（copy，备份下文件）3、gedit /etc/apt/sources.list（编辑源列表。
gedit，默认的文档编辑器）deb /ubuntu/ oneiric main universe restricted multiversedeb-src /ubuntu/ oneiric main universe restricted multiversedeb /ubuntu/ oneiric-security universe main multiverse restricteddeb-src /ubuntu/ oneiric-security universe main multiverse restricteddeb /ubuntu/ oneiric-updates universe main multiverse restricteddeb /ubuntu/ oneiric-proposed universe main multiverse restricteddeb-src /ubuntu/ oneiric-proposed universe main multiverse restricteddeb /ubuntu/ oneiric-backports universe main multiverse restricteddeb-src /ubuntu/ oneiric-backports universe main multiverse restricteddeb-src /ubuntu/ oneiric-updates universe main multiverse restricted4、apt-get update（更新源地址）更多Ubuntu 11.10 更新源地址列表：http://bolg.malu.me/wap/index-wap2.php?p=1190。
2）安装JDK6应用中心只有OpenJDK，不记得默认是否安装了==。
这个倒是不影响源码下载，但是在编译的某步会报缺少tool.jar的错误（jdk lib内的包）。
1、下载jdk&jre（jre可不需要）不需要用jdk7，以下是Java 6u29版本的相关地址。
jdk-6u29:/technetwork/java/javase/downloads/jdk-6u29-download-513648.htmljre-6u29:/technetwork/java/javase/downloads/jre-6u29-download-513650.html2、创建/usr/lib/jvm/java目录，并把下载的xxx.bin文件移到该目录。
sudo -s（或者在下述命令前加sudo，否则是动不了usr/lib下东西的）cd /usr/lib（进入/usr/lib）mkdir jvm（没有jvm，就这样创建）cd jvm（进入/usr/lib/jvm）mkdir java（没有java，就再创建）mv 文件绝对路径 /usr/lib/jvm/java（移动文件至/usr/lib/jvm/java）如：sudo mv ~/下载/jdk-6u29-linux-i586.bin /usr/lib/jvm/java3、安装jdk（配环境变量等）cd /usr/lib/jvm/java（说明是在该目录下罢了）chmod +x jdk-6u29-linux-i586.bin（增加可执行权限）Linux权限的解释：/article.asp?id=925，汗颜啊==./ jdk-6u29-linux-i586.bin（执行文件，会将jdk解压至当前文件夹）gedit /etc/environment（修改变量）用vi的话，最好先在文本编辑好。
:d删除当前那行，:i把复制内容输进去PATH=”……:$JAVA_HOME/bin”（……为原PATH）CLASSPATH=”.:$ JAVA_HOME/lib”JAVA_HOME=”/usr/lib/jvm/java/jdk1.6.0_29”source ~/.bashrc（设置变量）update-alternatives --install /usr/bin/java java/usr/lib/jvm/java/jdk1.6.0_29/bin/java 300update-alternatives --install /usr/bin/javac javac/usr/lib/jvm/java/jdk1.6.0_29/bin/javac 300（安装jdk至java选单）update-alternatives --config java（选择默认jdk）java –version（确认查看版本）更多参考网址：1、ubuntu安装jdk全过程（仅供参考）/viewtopic.php?t=1838032、ubuntu 11.10 安装 java环境/nikyxxx/archive/2011/11/11/2245897.htm l3）安装开发包具体什么不管了，当时执行的是这个^^。
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown libxml2-utils lib64z1-dev libc6-dev-amd64 g++-multilib lib64stdc++64）下载源码以下载android-4.0.3_r1至/home/<user name>/env/android_src/4.0.3_r1目录下为例。
cd ~/env/android_src/4.0.3_r1/（进入该目录，没有就mkdir）curl https:///dl/googlesource/git-repo/repo >repo（创建repo文件）sudo chmod a+x repo（增加可执行权限）./repo init -u https:///platform/manifest -b android-4.0.3_r1（初始化版本库为支线上的android-4.0.3_r1版本）Your Name [<user name>]:（会跳至这个，要求输入用户名，随意）Your Email [<user name>@xxx]：（继续要求输入邮箱，随意）Your identity is: xxx xxxis this correct [y/N]? y（确认用户名、邮箱）repo initialized in /home/join/env/android_src/4.0.3_r1（初始化完毕的提示）./repo sync（同步版本库，即开始下载）1、遇到异常时重执行./repo sync，卡主时先Ctrl+C中断再执行./repo sync，继续下载。
2、中断会造成no repository什么的，再次中断并把提示的目录删除再继续./repo sync。