Sep 23, 2012

Setup poky development environment

The following is to setup development environment for working on poky project.
1) Setup a working directory
mkdir data/poky -p

2) Check out the poky source code
cd data/poky
git init
git remote add yocto git://git.yoctoproject.org/poky.git
git remote update
git branch -b denzil yocto/denzil

3) Check out meta-intel for BSP developmen
mkdir data/poky/meta-intel -p
cd data/poky/meta-intel
git init
git remote add meta-intel git://git.yoctoproject.org/meta-intel.git
git remote update
git branch -b denzil meta-intel/denzil

4) Checkout poky-extras for kernel development
mkdir data/poky/poky-extras -p
cd data/poky/poky-extras
git init
git remote add poky-extras git://git.yoctoproject.org/poky-extras
git remote update
git checkout -b denzil poky-extras/denzil

5) Clone the kernel source code
cd data
git clone --bare git://git.yoctoproject.org/linux-yocto-3.2 linux-yocto-3.2.git

6) Then clone a local copy to make change on that kernel
git clone linux-yocto-3.2.git my-linux-yocto-3.2-work

6) Now we can start a yocto build and development. The layout should be
 [hieult@hieuletrung data]$ tree -L 2
.
├── linux-yocto-3.2.git
│   ├── branches
│   ├── config
│   ├── description
│   ├── HEAD
│   ├── hooks
│   ├── info
│   ├── objects
│   ├── packed-refs
│   └── refs
├── my-linux-yocto-3.2-work
│   ├── arch
│   ├── block
│   ├── COPYING
│   ├── CREDITS
│   ├── crypto
│   ├── Documentation
│   ├── drivers
│   ├── firmware
│   ├── fs
│   ├── include
│   ├── init
│   ├── ipc
│   ├── Kbuild
│   ├── Kconfig
│   ├── kernel
│   ├── lib
│   ├── MAINTAINERS
│   ├── Makefile
│   ├── mm
│   ├── net
│   ├── README
│   ├── REPORTING-BUGS
│   ├── samples
│   ├── scripts
│   ├── security
│   ├── sound
│   ├── tools
│   ├── usr
│   └── virt
└── poky
    ├── bitbake
    ├── documentation
    ├── LICENSE
    ├── meta
    ├── meta-demoapps
    ├── meta-hob
    ├── meta-intel
    ├── meta-skeleton
    ├── meta-yocto
    ├── oe-init-build-env
    ├── poky-extras
    ├── README
    ├── README.hardware
    └── scripts


URL: