A tutorial to set up your environment and Download Source Code

1. Build Setup Instructions

1.1 Setting up the Host Environment

Pre-Requisites

1.1.1          Install the following packages for setting up your host VM

The instructions provided below are meant to be executed via the command line on an Ubuntu machine:

$         sudo apt-get   install     build-essential gettext bison libfile-slurp-perl gawk libncurses-dev autoconf flex doxygen libtool automake   libpcre3-dev zlib1g-dev libbz2-dev subversion minicom putty libssl-dev rpm python-pexpect python-svn python-argparse vim tofrodos meld dos2unix cmake uuid-dev ruby transfig libglib2.0-dev xutils-dev lynx-cur gperf autopoint   python-dulwich   python-dev curl vim diffstat texinfo chrpath   openjdk-7-jre

1.1.2          Configure bash as default command interpreter for shell scripts

$         sudo dpkg-reconfigure dash

Select “No”
To choose bash, when the prompt asks if you want to use dash as the default system shell - select “No”

1.1.3         Configure Git

Upgrade your Git version to 1.8.x or higher

On Ubuntu 16.04 LTS, if you are unable to upgrade your git version using apt-get, then follow the below steps in order to upgrade  

$       sudo apt-get install python-software-properties

$       sudo add-apt-repository   ppa:git-core/ppa

$       sudo apt-get update

$       sudo apt-get install git

  Once git is installed, configure your name and email using the below commands

$ git config --global user.email " you@example.com "

$ git config --global user.name "Your Name"

1.1.4          Configure repo

In order to use Yocto build system, first you need to make sure that repo is properly installed on the machine:

$ mkdir ~/bin

$ PATH=~/bin:$PATH

$ curl   https://storage.googleapis.com/git-repo-downloads/repo   > ~/bin/repo

$ chmod a+x ~/bin/repo

Trivia : Repo is a repository management tool that is built on top of Git. Its main purpose is to help manage projects that consist of many Git repositories, it can also be used to manage uploads to the CMF Gerrit instance and automate aspects of the development workflow.

Repo does not replace Git, it simply aids management of projects that contain multiple Git repositories into a single local working directory. Git will still be used for local operation such as commits etc.

Repo manages this for you by means of an XML based Manifest file. The Manifest file defines which repositories the project uses and links to appropriate revisions of each git repository, i.e where the upstream repositories reside and where they should be cloned locally. It is the manifest.xml (or default.xml) that determines which Git repositories and revisions repo will manage. This manifest.xml file is hosted in a Git repository along with all the other git repositories.

1.2         Downloading Source Code & Building

 1.2.1          Downloading Source Code

Following commands fetch the source code of emulator using repo tool

$ mkdir <Directory-Name> && cd <Directory-Name>

Please use the following repo init command

$ repo init -u https://user@code.rdkcentral.com/r/manifests -m manifest.xml -b <branch_name>

Examples :

repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20180527

repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b master

repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b morty

$ repo sync -j4 --no-clone-bundle

1.2.2          Building

$ source <setup-environment>

The above step configures and sets up your directory to start an appropriate build for broadband.

There are different kinds of builds listed. Please read the options and select the number of the build you need.

1) meta-rdk-bsp-emulator/conf/machine/qemuarmbroadband.conf
2) meta-rdk-bsp-emulator/conf/machine/qemux86broadband.conf
3) meta-rdk-bsp-emulator/conf/machine/qemux86hyb.conf
4) meta-rdk-bsp-emulator/conf/machine/qemux86mc.conf
5) openembedded-core/meta/conf/machine/qemuarm.conf
6) openembedded-core/meta/conf/machine/qemux86-64.conf
7) openembedded-core/meta/conf/machine/qemux86.conf

Next, you would need to initiate the build using the following command:

$ bitbake <image-name>

On Successful build, the ROOTFS (in vmdk format) would be available at the following reference location based on the build type :

-$ {HOME}/emulator/build-qemux86broadband/tmp/deploy/images/qemux86broadband/rdk-generic-broadband-image-qemux86broadband-<timestamp>.vmdk

Example:  

…/build-qemux86broadband/tmp/deploy/images/qemux86broadband/rdk-generic-broadband-image-qemux86broadband-20160217080610.vmdk