Table of Contents
Advertisement
6.3.2 Initializing build environment
Once the layers have been properly cloned in their appropriate branch, the build environment needs to be
initialized. This can be done by running the following command:
source
poky/oe-init-build-env build
This will initialize the build environment by making the bitbake build tool available in the current shell and
creating a build directory where temporary and final build artifacts will be stored.
The following directory layout should be observed:
yocto
build
meta-arm
meta-openembedded
meta-rockchip
meta-theobroma-systems-bsp
meta-theobroma-systems-extended
poky
The first time the command is run, it'll create a new build directory called build and add the appropriate con-
figuration files. On the later runs, if the directory still exists, the command will only configure the terminal
environment and not change anything in the build directory. This makes it perfectly safe to run the command
multiple times, from different terminals for example.
Note: Once the current terminal is closed or a new one is opened, this command should be re-executed to be
able to interact again with the Yocto Project tools.
The Yocto Project then needs to be configured to include layers to find new recipes or configuration files, which
is essential to build new pieces of software or compile for a specific hardware target system.
This can be done with the bitbake-layers tool:
bitbake-layers add-layer ../meta-arm/meta-arm-toolchain
bitbake-layers add-layer ../meta-arm/meta-arm
bitbake-layers add-layer ../meta-rockchip
bitbake-layers add-layer ../meta-openembedded/meta-oe
bitbake-layers add-layer ../meta-openembedded/meta-python
bitbake-layers add-layer ../meta-openembedded/meta-networking
bitbake-layers add-layer ../meta-theobroma-systems-bsp
bitbake-layers add-layer ../meta-theobroma-systems-extended
6.3.3 Building an image
To build a bootable artifact, BitBake will be called with the specified machine and target image:
MACHINE="jaguar"
bitbake theobroma-extended-image
Note: Technically speaking, the MACHINE variable could be set in build/conf/local.conf file once and for all.
If possible, Theobroma Systems recommends passing the variable explicitly in the command directly as this
makes it more visible to the user and also allows to easily build for multiple machines without modifying a file
in-between.
The build process can take several hours depending on the capabilities of the build machine and the user's
Internet connection.
Note: If the Bitbake process needs to be stopped for any reason, a SIGINT (Ctrl + c) signal can be sent once.
Bitbake will gracefully close down upon reception of this signal. This graceful shutdown can take a lot of time
v1.0.1
Page 22
Advertisement
Table of Contents
