Compiling yocto poky for qemuarm and running qemuarm

Below steps defines the procedure for compiling yocto poky source for building qemu arm binaries

$ mkdir ~/Desktop/devlab/yocto/metadata/

$ cd ~/Desktop/devlab/yocto/metadata/

$ git clone git://git.yoctoproject.org/poky poky

$ cd poky

$ git checkout -b fido origin/fido

Here, we have used poky / yocto fido version,

$ cd ~/Desktop/devlab/yocto/metadata/

$ mkdir build

$ source oe-init-build-env ~/Desktop/devlab/yocto/metadata/build

You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to use a
different MACHINE (target hardware) or enable parallel build options to take
advantage of multiple cores for example. See the file for more information as
common configuration options are commented.

You had no conf/bblayers.conf file. The configuration file has been created for
you with some default values. To add additional metadata layers into your
configuration please add entries to this file.

READ  fix yocto QA Issue : " was already stripped, this will prevent future debugging ! "

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/
### Shell environment set up for builds. ###

You can now run ‘bitbake <target>’

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
adt-installer
meta-ide-support

You can also run generated qemu images with a command like ‘runqemu qemux86’

This will create 2 main files named, conf/local.conf & conf.bblayer.conf as inside build directory.

build$ tree
.
`– conf
|– bblayers.conf
|– local.conf
`– templateconf.cfg

Now, open the conf/local.conf file and change MACHINE ?= “qemuarm” by disabling other MACHINE types.

$ bitbake core-image-minimal

Leave a Reply

Your email address will not be published. Required fields are marked *