Create a new layer in Yocto - Manual/Script

-
What is a layer in Yocto?

 A layer contains meta data. meta data means configuration files, classes and recipes. Layers allow you to isolate different type of customizations from each other.

When you clone the poky source code.
$ git clone -b thud git://git.yoctoproject.org/poky.git

 You already have the following layers:

  • meta
  • meta-skeleton
  • meta-yocto-bsp
  • meta-poky
  • meta-selftest
You may need to include additional layers as per your requirement for example, if you are building image for raspberry pi3 you need to add the layer: meta-raspberrypi

Two ways to add an existing layer:
1. Manual: Add the existing layer path inside BBLAYERS variable in conf/bblayers.conf file
2. Using script: bitbake-layers add-layer <path to existing layer>. This will update bblayers.conf file.

You can find existing layers on layers.openembedded.org.

If you don't find a layer with the recipes you need, you can also create your own layer. There are two ways to create your own layer.
1. Manually
2. Using script

Manually:
  • Create a directory for the layer. For example: 'meta-mylayer'
  • Inside this directory, create conf/local.conf with the following contents.


Using Script:

Initialize the build environment: source poky/oe-init-build-env build > /dev/null
Run the command 'bitbake-layers create-layer meta-mylayer' to create a new layer automatically


In either of the approach, you need to add this newly created layer in conf/bblayers.conf file for the recipes to be included in the bitbake path.

Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
Read more