Table of Contents
Advertisement
yocto
meta-arm
meta-openembedded
meta-rockchip
meta-theobroma-systems-bsp
poky
Note: It is essential that the Yocto layers are checked out on the same branch otherwise there may be some unexpected issues.
With the aforementioned instructions, the layers have been checked out to a branch supporting the Yocto Project Kirkstone
(4.0) release.
6.2.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, making bitbake build tool available in the current shell, and also create a build
directory where temporary and final build artefacts will be stored.
The following directory layout should be observed:
yocto
build
meta-arm
meta-openembedded
meta-rockchip
meta-theobroma-systems-bsp
poky
The first time the command is run, it'll create a new build directory called build and add the appropriate configuration 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-theobroma-systems-bsp
6.2.3 Building a minimal image
To build a bootable artefact, BitBake will be called with the specified machine and target image:
MACHINE="ringneck-haikou"
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
v1.2.0-1-g5ccabb6
Page 24
bitbake core-image-minimal
Advertisement
Table of Contents
