MSM8xxx enviroment set up guide



1. Installation and Setup

1.1. Ubuntu Installation
Install 64-bit Ubuntu 12.04 LTS on your PC by CD. Set language to English, or may have
problems when building the source code. The source code will be downloaded later is about 50GB,
make sure you have enough disk space.
1.2. Setting Up a Linux Build Environment
1.2.1. Installing the JDK
(1) Download jdk-6u45-linux-x64.bin in:
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloadsjavase6-
419409.html.
(2) Change the mode under the download directory:
$ chmod +x jdk-6u45-linux-x64.bin.
(3) Execute the installation script in the directory where you want the jdk package installed
(this creates a directory under the directory where you executed the installation script):
$ mkdir -p /opt/jdk6
$ cd /opt/jdk6
$ ./jdk- <xxx>.bin
(4) Override the use of any other installed jdk by adding <jdk_installdir>/ bin to the front of
your path.
$ export PATH=/opt/jdk6/jdk<xxx>/bin:$PATH
NOTE: Include the above path setting in your .bash_profile, so it is set automatically every
time you log in.
1.2.2. Installing Required Packages
Use apt-get to install the additional required packages.

$ sudo apt-get install git 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-ltsquantal:
i386 \ libgl1-mesa-dev g++-multilib mingw32 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
1.2.3. Repo Installation
The repo tool is a source code configuration management tool used by the Android project. It is
a front end to git written in Python that uses a manifest file to aid downloading code organized as a
set of projects stored in different git repositories.
To install repo:
(1) Create a ~/bin directory in your home directory, or, if you have root or sudo access, install
for all system users under a common location, such as /usr/local/bin or somewhere under /opt.
(2) Download the repo script.
$ curl http://android.git.kernel.org/repo >~/bin/repo
(3) Set the repo script’s attributes to executable.
$ chmod a+x ~/bin/repo
(4) Make sure that the installed directory location for repo is included in your PATH.
$ export PATH=~/bin:$PATH
(5) Try running repo -- help to verify installation; you should see a message similar to the
following:
$ repo --help
usage: repo COMMAND [ARGS]
repo is not yet installed. Use "repo init" to inst all it here.
The most commonly used repo commands are:
init Install repo in the current working directory
help Display detailed help on a command
(6) For access to the full online help, install repo(repo init).

2. Software Product Information
2.1. Access to the Software
2.1.1. Downloading Qualcomm Technologies, Inc. Proprietary Software
The non-HLOS and proprietary HLOS software releases are distributed via Qualcomm
ChipCodeTM. ChipCode is the new distr ibution system for QMC software and replaces the
CDMATech Support Documents and Downloads site for licensees.
Designated points of contact at customer sites are given access to download software for which
the customer has a current license.
Each customer will have access to a set of distros for the chipsets for which they are licensed.
For each distro, there is a Git project and the Git tree will include revisions for previous builds,
allowing OEMs to diff the changes between releases via Git.
2.1.2. Downloading Open Source HLOS Software
The Linux Board Support Package(BSP) release will be obtained in two parts, a proprietary
release from the CDMATech Support Documents and Downloads site and an open source release
from the Code Aurora Forum(CAF) site.
To download the open source software:
(1) Look in your Release Notes and note the build ID indicated on the title page.
(2) Go to https://www.codeaurora.org/xwiki/bin/QAEP/ and find the release branch containing
the matching build ID in the branch releases table. The release area that lists all builds is here:
https://www.codeaurora.org/xwiki/bin/QAEP/release.
(3) In an empty workspace directory, issue the repo init command with the correct branch and
manifest as indicated in the branch releases table.
(4) Type the repo sync command.

$ repo sync
(5) After the repo sync finishes, copy the vendor/qcom/proprietary directory tree from the
proprietary HLOS release into the open source HLOS source tree contained in your workspace

Done^^^^^