Poky

https://github.com/yoctoproject/poky
Admin
Poky is a pre-packaged build system and development environment for the Yocto Project, used for...
Tokens:248,348
Snippets:2,321
Trust Score:6.8
Update:11 months ago
Show doc for...
Tokens:
Raw
### Standard SDK Installer Example (Bash)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/using.rst

An example command to execute the Standard SDK installer script. This script guides the user through the installation process, allowing them to specify the target directory for the SDK. After installation, an environment setup script needs to be sourced to use the SDK.

```bash
$ ./Downloads/poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
Poky (Yocto Project Reference Distro) SDK installer version &DISTRO;
===============================================================
Enter target directory for SDK (default: /opt/poky/&DISTRO;):
You are about to install the SDK to "/opt/poky/&DISTRO;". Proceed [Y/n]? Y
Extracting SDK........................................ ..............................done
Setting it up...done
SDK has been successfully set up and is ready to be used.
Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.
 $ . /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
```

--------------------------------

### Start Toaster for Local Development (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

Commands to set up the build environment and start the Toaster web interface for local development. Assumes Yocto Project and Toaster dependencies are already installed.

```shell
$ cd poky
$ source oe-init-build-env
$ source toaster start
```

--------------------------------

### Start Basic Hash Equivalence Server (Bash)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/hashequivserver.rst

This command starts a basic Hash Equivalence server using default options. It's the simplest way to get a local server running. The script is located in the BitBake repository.

```bash
./bin/bitbake-hashserv
```

--------------------------------

### Installing Apache, mod_wsgi, and MariaDB on Fedora/RedHat (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

This command installs required packages for a production Toaster setup on Fedora or RedHat-based systems, including httpd (Apache), mod_wsgi, python3-pip, and MariaDB server.

```bash
$ sudo dnf install httpd python3-mod_wsgi python3-pip mariadb-server mariadb-devel python3-devel
```

--------------------------------

### Yocto BitBake do_install Function Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/new-recipe.rst

An example of a do_install function in a Yocto Project BitBake recipe, specifically from the 'sed' recipe. This function uses shell commands to create directories and move executables, demonstrating how to manage installed files within the destination directory structure ('${D}').

```bitbake
do_install () {
    autotools_do_install
    install -d ${D}${base_bindir}
    mv ${D}${bindir}/sed ${D}${base_bindir}/sed
    rmdir ${D}${bindir}/
}
```

--------------------------------

### Source SDK Environment Setup Script (Bash)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/using.rst

This command sources the SDK environment setup script. It configures the necessary environment variables for using the SDK. The script name includes the target architecture (e.g., i586-poky-linux). Ensure you are in the SDK's installation directory before running.

```bash
$ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
```

--------------------------------

### Simulate OS Image with QEMU

Source: https://github.com/yoctoproject/poky/blob/master/documentation/brief-yoctoprojectqs/index.rst

Starts a QEMU (Quick EMUlator) instance to simulate the built OS image on a virtual hardware target. This is useful for testing without physical hardware. Requires QEMU to be installed and the image to be built.

```shell
$ runqemu qemux86-64
```

--------------------------------

### IMAGE_BOOT_FILES Configuration Examples

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/variables.rst

Demonstrates how to configure the IMAGE_BOOT_FILES variable, which specifies files to be installed into the boot partition for image generation using the Wic tool. It shows basic file installation and renaming using a semicolon.

```shell
IMAGE_BOOT_FILES = "u-boot.img uImage;kernel"
IMAGE_BOOT_FILES = "u-boot.${UBOOT_SUFFIX} ${KERNEL_IMAGETYPE}"
```

--------------------------------

### Check and Start VirtualBox Guest Additions Service (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/meta/recipes-core/images/build-appliance-image/README_VirtualBox_Guest_Additions.txt

These commands check the status of the VirtualBox Guest Additions service and provide a way to manually start it if it's not running. This is part of the verification process after installation.

```shell
# /etc/init.d/vboxadd status
# /etc/init.d/vboxadd start
```

--------------------------------

### Raspberry Pi Xorg Configuration Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/bsp-guide/bsp.rst

This file provides an example Xorg configuration for Raspberry Pi. It includes settings for the evdev input driver, touchscreen calibration, and specific configurations for PiTFT displays.

```xorg.conf
# /etc/X11/xorg.conf.d/10-evdev.conf
Section "InputClass"
    Identifier "evdev touchscreen"
    MatchIsTouchscreen "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

# /etc/X11/xorg.conf.d/98-pitft.conf
Section "Device"
    Identifier "PiTFT"
    Driver "fbdev"
    Option "fbdev" "/dev/fb1"
EndSection

# /etc/X11/xorg.conf.d/99-calibration.conf
Section "InputClass"
    Identifier "calibration touchscreen"
    MatchIsTouchscreen "on"
    Driver "libinput"
    Option "CalibrationTransform" "0 0 0 0 0 0"
EndSection

```

--------------------------------

### Initialize Cross-Development Environment

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/appendix-obtain.rst

Example of sourcing the cross-development environment setup script. This script is typically found in the top-level directory where the toolchain was installed.

```shell
source <install_dir>/environment-setup-<target-machine>
```

--------------------------------

### CMake Executable and Test Setup

Source: https://github.com/yoctoproject/poky/blob/master/meta-selftest/recipes-test/cpp/files/CMakeLists.txt

This snippet defines an executable 'cmake-example' that links against the custom library and is installed to the binary directory. It also sets up a test executable 'test-cmake-example' for testing the library, conditionally defining a macro for failing tests, and installing the test executable.

```cmake
# A simple executable linking the library
add_executable(cmake-example cpp-example.cpp)
target_link_libraries(cmake-example PRIVATE cmake-example-lib)

install(TARGETS cmake-example
    RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
)

# A simple test executable for testing the library
add_executable(test-cmake-example test-cpp-example.cpp)
target_link_libraries(test-cmake-example PRIVATE cmake-example-lib)

if (FAILING_TEST)
    target_compile_definitions(test-cmake-example PRIVATE FAIL_COMPARISON_STR="foo")
endif(FAILING_TEST)

install(TARGETS test-cmake-example
    RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
)
```

--------------------------------

### BeagleBone Yocto BSP Machine Configuration Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/bsp-guide/bsp.rst

This example demonstrates a machine configuration file for the BeagleBone, BeagleBone Black, and BeagleBone Green boards. It specifies kernel, bootloader, image types, and crucial hardware-specific settings like serial consoles and machine features. It also includes configurations for `runqemu` integration.

```bitbake
#@TYPE: Machine
#@NAME: Beaglebone-yocto machine
#@DESCRIPTION: Reference machine configuration for http://beagleboard.org/bone and http://beagleboard.org/black boards

PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"

MACHINE_EXTRA_RRECOMMENDS = "kernel-modules"

EXTRA_IMAGEDEPENDS += "virtual/bootloader"

DEFAULTTUNE ?= "cortexa8hf-neon"
include conf/machine/include/arm/armv7a/tune-cortexa8.inc

IMAGE_FSTYPES += "tar.bz2 jffs2 wic wic.bmap"
EXTRA_IMAGECMD:jffs2 = "-lnp "
WKS_FILE ?= "beaglebone-yocto.wks"
MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "kernel-image kernel-devicetree"
do_image_wic[depends] += "mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot virtual/bootloader:do_deploy"

SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0 115200;ttyAMA0"

PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
PREFERRED_VERSION_linux-yocto ?= "6.12%"

KERNEL_IMAGETYPE = "zImage"
DTB_FILES = "am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb"
KERNEL_DEVICETREE = "${@'.join('ti/omap/%s' % d for d in '${DTB_FILES}'.split())}"

PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"

SPL_BINARY = "MLO"
UBOOT_SUFFIX = "img"
UBOOT_MACHINE = "am335x_evm_defconfig"

MACHINE_FEATURES = "usbgadget usbhost vfat alsa"

IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} ${SPL_BINARY} ${KERNEL_IMAGETYPE} ${DTB_FILES}"

# support runqemu
EXTRA_IMAGEDEPENDS += "qemu-native qemu-helper-native"
IMAGE_CLASSES += "qemuboot"
QB_DEFAULT_FSTYPE = "wic"
QB_FSINFO = "wic:no-kernel-in-fs"
QB_KERNEL_ROOT = "/dev/vda2"
QB_SYSTEM_NAME = "qemu-system-arm"
QB_MACHINE = "-machine virt"
QB_CPU = "-cpu cortex-a15"
QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0 systemd.mask=systemd-networkd"
QB_OPT_APPEND = "-device virtio-rng-device"
QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device virtio-blk-device,drive=disk0"
QB_SERIAL_OPT = ""
QB_TCPSERIAL_OPT = "-device virtio-serial-device -chardev socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device virtconsole,chardev=virtcon"

```

--------------------------------

### Basic Yocto Recipe for Binary Package Installation

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/new-recipe.rst

An example of a Yocto Project recipe for handling binary packages. This recipe fetches a single tarball, inherits 'bin_package' and 'allarch', and defines a do_install function to manually install the binary files and associated directories. It does not require separate configuration or compilation steps.

```bitbake
SRC_URI = "https://www.kernel.org/pub/software/network/${BPN}/${BP}.tar.xz"
SRC_URI[sha256sum] = "57f8e7721cf5a880c13ae0c202edbb21092a060d45f9e9c59bcd2a8272bfa456"

inherit bin_package allarch

do_install() {
    install -d -m0755 ${D}${nonarch_libdir}/crda
    install -d -m0755 ${D}${sysconfdir}/wireless-regdb/pubkeys
    install -m 0644 regulatory.bin ${D}${nonarch_libdir}/crda/regulatory.bin
    install -m 0644 wens.key.pub.pem ${D}${sysconfdir}/wireless-regdb/pubkeys/wens.key.pub.pem
    install -m 0644 -D regulatory.db ${D}${nonarch_base_libdir}/firmware/regulatory.db
    install -m 0644 regulatory.db.p7s ${D}${nonarch_base_libdir}/firmware/regulatory.db.p7s
}
```

--------------------------------

### Run SDK Installer Script

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/appendix-obtain.rst

Example command to execute the SDK installer script. The installer script is located in the 'tmp/deploy/sdk' directory within the build directory.

```shell
cd poky/build/tmp/deploy/sdk
./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
```

--------------------------------

### BitBake Version String Example (Historical Pre-release)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/contributor-guide/recipe-style-guide.rst

Shows a historical syntax for version strings in BitBake, combining prior and pre-release versions. The tilde form is preferred.

```BitBake
PV = "1.4+1.5rc2"
```

--------------------------------

### Raspberry Pi BSP Layer File Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/bsp-guide/bsp.rst

Provides a detailed file listing for the meta-raspberrypi BSP layer, showcasing the organization of configuration files, classes, and recipes specific to Raspberry Pi hardware.

```none
meta-raspberrypi/COPYING.MIT
meta-raspberrypi/README.md
meta-raspberrypi/classes
meta-raspberrypi/classes/sdcard_image-rpi.bbclass
meta-raspberrypi/conf/
meta-raspberrypi/conf/layer.conf
meta-raspberrypi/conf/machine/
meta-raspberrypi/conf/machine/raspberrypi-cm.conf
meta-raspberrypi/conf/machine/raspberrypi-cm3.conf
meta-raspberrypi/conf/machine/raspberrypi.conf
meta-raspberrypi/conf/machine/raspberrypi0-wifi.conf
meta-raspberrypi/conf/machine/raspberrypi0.conf
meta-raspberrypi/conf/machine/raspberrypi2.conf
meta-raspberrypi/conf/machine/raspberrypi3-64.conf
meta-raspberrypi/conf/machine/raspberrypi3.conf
meta-raspberrypi/conf/machine/include
meta-raspberrypi/conf/machine/include/rpi-base.inc
meta-raspberrypi/conf/machine/include/rpi-default-providers.inc
meta-raspberrypi/conf/machine/include/rpi-default-settings.inc
meta-raspberrypi/conf/machine/include/rpi-default-versions.inc
meta-raspberrypi/conf/machine/include/tune-arm1176jzf-s.inc
meta-raspberrypi/docs
meta-raspberrypi/docs/Makefile
meta-raspberrypi/docs/conf.py
meta-raspberrypi/docs/contributing.md
meta-raspberrypi/docs/extra-apps.md
meta-raspberrypi/docs/extra-build-config.md
meta-raspberrypi/docs/index.rst
meta-raspberrypi/docs/layer-contents.md
meta-raspberrypi/docs/readme.md
meta-raspberrypi/files
meta-raspberrypi/files/custom-licenses
meta-raspberrypi/files/custom-licenses/Broadcom
meta-raspberrypi/recipes-bsp
meta-raspberrypi/recipes-bsp/bootfiles
meta-raspberrypi/recipes-bsp/bootfiles/bcm2835-bootfiles.bb
meta-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bb
meta-raspberrypi/recipes-bsp/common
meta-raspberrypi/recipes-bsp/common/firmware.inc
meta-raspberrypi/recipes-bsp/formfactor
meta-raspberrypi/recipes-bsp/formfactor/formfactor
meta-raspberrypi/recipes-bsp/formfactor/formfactor/raspberrypi
meta-raspberrypi/recipes-bsp/formfactor/formfactor/raspberrypi/machconfig
```

--------------------------------

### Source Yocto SDK Environment Setup Script

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/extensible.rst

Commands to navigate to the SDK installation directory and source the environment setup script. This script configures the shell environment variables required to use the SDK, such as PATH and compiler settings. It is essential to run this script in each new shell session before using SDK tools like 'devtool'.

```shell
$ cd /home/scottrif/poky_sdk
$ source environment-setup-core2-64-poky-linux
```

--------------------------------

### Install Standard SDK Tarball (Bash)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/using.rst

Installs the Yocto Project Standard SDK using a provided tarball installer script. This script unpacks the toolchain, runqemu script, and support files, and sets up the SDK environment. The installation location must be writable by users.

```bash
$ .	/opt/poky/&DISTRO;/environment-setup-i586-poky-linux
```

--------------------------------

### Check BitBake Version

Source: https://github.com/yoctoproject/poky/blob/master/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.rst

This command verifies the installation and version of the BitBake build tool. It's a fundamental step to ensure BitBake is accessible and operational in your environment.

```bash
./bin/bitbake --version
```

--------------------------------

### Generate and Use Yocto SDK for Cross-Compilation

Source: https://context7.com/yoctoproject/poky/llms.txt

Instructions for building, installing, and sourcing the Yocto SDK. Includes examples for cross-compiling applications and using SDK tools like the cross-compiler, archiver, stripper, and pkg-config.

```bash
# Build standard SDK
bitbake core-image-minimal -c populate_sdk

# Build extensible SDK (includes devtool)
bitbake core-image-minimal -c populate_sdk_ext

# Install SDK (from generated installer script)
./tmp/deploy/sdk/poky-glibc-x86_64-core-image-minimal-cortexa8hf-neon-qemuarm-toolchain-5.1.sh

# Source SDK environment
source /opt/poky/5.1/environment-setup-cortexa8hf-neon-poky-linux-gnueabi

# Cross-compile application with SDK
$CC -o myapp myapp.c
file myapp
# myapp: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV)

# Use SDK tools
$AR rcs libmylib.a mylib.o
$STRIP myapp
$RANLIB libmylib.a

# PKG-config with SDK
$PKG_CONFIG --cflags --libs glib-2.0
```

--------------------------------

### BitBake Version String Example (Pre-release)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/contributor-guide/recipe-style-guide.rst

Demonstrates the preferred method for specifying pre-release versions in BitBake, using the tilde (~) operator for correct sorting.

```BitBake
PV = "1.5~rc2"
```

--------------------------------

### Example Yocto Recipe for Unversioned Library

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/prebuilt-libraries.rst

A sample Yocto recipe for installing an unversioned x86-64 pre-built library named libfoo.so. It includes settings for COMPATIBLE_HOST, QA exceptions, and the necessary SOLIBS and FILES_SOLIBSDEV modifications for correct packaging.

```bitbake
SUMMARY = "libfoo sample recipe"
SECTION = "libs"
LICENSE = "CLOSED"

SRC_URI = "file://libfoo.so"

COMPATIBLE_HOST = "x86_64.*-linux"

INSANE_SKIP:${PN} = "ldflags"
INHIBIT_PACKAGE_STRIP = "1"
INHIBIT_SYSROOT_STRIP = "1"
SOLIBS = ".so"
FILES_SOLIBSDEV = ""

do_install () {
        install -d ${D}${libdir}
        install -m 0755 ${UNPACKDIR}/libfoo.so ${D}${libdir}
}
```

--------------------------------

### Installing Apache, mod_wsgi, and MariaDB on openSUSE (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

This command installs essential packages for running Toaster on openSUSE, including the Apache web server, mod_wsgi, python3-pip, and MariaDB.

```bash
$ sudo zypper install apache2 apache2-mod_wsgi-python3 python3-pip mariadb mariadb-client python3-devel
```

--------------------------------

### List WSL 2 Distributions

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/start.rst

This command lists the installed Linux distributions within WSL 2 and their current states (running or stopped). It helps verify the Linux environment setup.

```shell
C:\WINDOWS\system32> wsl -l -v
NAME    STATE   VERSION
*Ubuntu Running 2
```

--------------------------------

### Getting Wic Command Help

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/wic.rst

This snippet shows the general method for obtaining help on any `wic` command. By appending `help` to the command name, users can access detailed usage information, options, and examples for that specific command.

```bash
$ wic help ls
```

--------------------------------

### GenericX86 Kickstart File Partition Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/wic.rst

Example of partition definitions within a genericx86.wks kickstart file. It defines partitions for boot, root filesystem, and swap, along with bootloader configuration.

```kickstart
# short-description: Create an EFI disk image for genericx86*
# long-description: Creates a partitioned EFI disk image for genericx86* machines
part /boot --source bootimg_efi --sourceparams="loader=grub-efi" --ondisk sda --label msdos --active --align 1024
part / --source rootfs --ondisk sda --fstype=ext4 --label platform --align 1024 --use-uuid
part swap --ondisk sda --size 44 --label swap1 --fstype=swap

bootloader --ptable gpt --timeout=5 --append="rootfstype=ext4 console=ttyS0,115200 console=tty0"
```

--------------------------------

### Run Yocto SDK Installer

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/extensible.rst

Command to execute the Yocto Project's extensible SDK installer script. Assumes the installer is in the Downloads directory and has execute permissions. The installer prompts for the target installation directory.

```shell
$ ./Downloads/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.5.sh
```

--------------------------------

### Wic Raw Mode Command Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/wic.rst

Example of using Wic in 'raw mode' with an existing kickstart file (directdisk) and specifying directories for rootfs, boot images, kernel, and sysroot.

```bash
$ wic create directdisk -r rootfs_dir -b bootimg_dir \
      -k kernel_dir -n native_sysroot
```

--------------------------------

### Specify Barebox Binary for Deployment

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/variables.rst

This example illustrates the use of the BAREBOX_BINARY variable within the :ref:`ref-classes-barebox` class. It allows specifying a particular Barebox binary to be deployed and installed when multiple binaries are built.

```bitbake
BAREBOX_BINARY = "barebox-boundarydevices-imx6dl-nitrogen6x-1g.img"
```

--------------------------------

### Running QEMU Emulator with Machine Name

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/qemu.rst

This example illustrates the basic command to start QEMU for a specified machine (e.g., 'qemux86-64'). The 'runqemu' script automatically locates the appropriate kernel and root filesystem images from the build directory based on the machine name and timestamps.

```shell
runqemu qemux86-64
```

--------------------------------

### Yocto Kernel Configuration Options Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/kernel-dev/concepts-appx.rst

This snippet demonstrates how to specify hardware-related kernel configuration options using a .cfg file within the Yocto kernel build system. These configurations are essential for ensuring proper hardware support and preventing boot failures.

```text
CONFIG_SERIAL_8250
CONFIG_SERIAL_8250_CONSOLE
```

--------------------------------

### Yocto Project: Example local.conf Configuration

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/structure.rst

Illustrates basic configuration within the `local.conf` file for a Yocto Project build. Key variables include `MACHINE` for the target hardware, `PACKAGE_CLASSES` for package management, and `DL_DIR` for download location. Variables can be hard-coded using '='.

```conf
# Example local.conf settings
MACHINE ?= "qemux86-64"
PACKAGE_CLASSES ?= "package_rpm"
DL_DIR ?= "${TOPDIR}/downloads"

```

--------------------------------

### Running QEMU with Basic Options

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/qemu.rst

Illustrates fundamental `runqemu` command examples for launching QEMU. These examples showcase how to specify machine types, image paths, and basic console configurations like `nographic` or `serial` for different emulation scenarios.

```shell
$ runqemu
$ runqemu qemuarm
$ runqemu tmp/deploy/images/qemuarm
$ runqemu qemux86-64 core-image-sato ext4
$ runqemu qemux86-64 wic-image-minimal wic
$ runqemu path/to/bzImage-qemux86.bin path/to/nfsrootdir/ serial
$ runqemu qemux86 iso/hddimg/wic.vmdk/wic.qcow2/wic.vdi/ramfs/cpio.gz...
$ runqemu path/to/<image>-<machine>.wic
$ runqemu path/to/<image>-<machine>.wic.vmdk
```

--------------------------------

### Example of GDB using debuginfod

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/debugging.rst

Demonstrates how GDB automatically fetches separate debug info when debuginfod is configured. The process involves starting GDB with the target binary, and if symbols are not found locally, debuginfod will attempt to download them.

```shell
root@qemux86-64:~# gdb /bin/cat
... 
Reading symbols from /bin/cat...
Downloading separate debug info for /bin/cat...
Reading symbols from /home/root/.cache/debuginfod_client/923dc4780cfbc545850c616bffa884b6b5eaf322/debuginfo...
```

--------------------------------

### Source Yocto SDK Environment Script

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/working-projects.rst

Demonstrates how to source the Yocto Project SDK environment setup script. This command is essential for setting up the necessary cross-compilation toolchain environment variables in the current shell session. Two examples are provided: one for a standard SDK installation and another for an in-build environment setup.

```bash
$ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
```

```bash
$ source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux
```

--------------------------------

### Starting Toaster Django Web Server (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

Shell commands to initialize the build environment and start the Toaster Django web server. This allows for testing and using the Toaster web interface with the MySQL database.

```shell
$ source oe-init-build-env
$ source toaster start
```

--------------------------------

### Initializing SDK Toolchain Environment

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/qemu.rst

This snippet demonstrates how to set up the environment when a cross-toolchain has been installed. It involves running a script that initializes the toolchain, specific to the target architecture and distribution.

```shell
. poky_sdk/environment-setup-core2-64-poky-linux
```

--------------------------------

### Run QEMU with Minimal Configuration

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/qemu.rst

This example demonstrates a minimal runqemu command. It requires at least a MACHINE, KERNEL, or VM option to launch QEMU successfully, as it only provides a root filesystem type.

```none
runqemu ext4
```

--------------------------------

### Wic Cooked Mode Command Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/wic.rst

Example command for running Wic in 'cooked mode', which utilizes artifacts from the Build Directory. Requires a kickstart file and the image name.

```bash
$ wic create wks_file -e IMAGE_NAME
```

--------------------------------

### Manual Installation in Yocto Recipes

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/new-recipe.rst

This snippet illustrates a manual installation process within a Yocto recipe. It involves explicitly creating target directories using 'install -d' and then copying built software into these directories using the 'install' command. This method is used when the build system doesn't automatically handle installation.

```bitbake
do_install()
{
    install -d ${"D"}/path/to/destination
    install -m 0755 built_file ${"D"}/path/to/destination/
}
```

--------------------------------

### Setting Up Yocto Project Build Environment

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/qemu.rst

This snippet shows how to initialize the build environment for the Yocto Project when using a cloned 'poky' repository or a downloaded release tarball. It involves navigating to the 'poky' directory and sourcing the environment setup script.

```shell
cd poky
source oe-init-build-env
```

--------------------------------

### Set Locales for Image Installation (BitBake)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/variables.rst

This example shows how to specify the list of locales to be installed in the image using the IMAGE_LINGUAS variable. The build system automatically handles locale package installation based on the specified language codes. The format is a space-separated string of locale identifiers.

```bitbake
IMAGE_LINGUAS = "pt-br de-de"
```

--------------------------------

### Toaster Database Schema and Static Files Setup (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

Shell commands to navigate to the Toaster directory, run database migrations, check settings, and collect static files. These commands ensure the database schema is up-to-date and static assets are collected for the web server.

```shell
$ cd /var/www/toaster/poky/
$ ./bitbake/lib/toaster/manage.py migrate
$ TOASTER_DIR=`pwd` TEMPLATECONF='poky' \
   ./bitbake/lib/toaster/manage.py checksettings
$ ./bitbake/lib/toaster/manage.py collectstatic
```

--------------------------------

### Customizing SDK Installer Title in Poky

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/appendix-customizing.rst

This example demonstrates how to set a custom title for the SDK installer by overriding the SDK_TITLE variable within a custom distribution configuration file (e.g., mymydistro.conf).

```bitbake
SDK_TITLE = "your_title"
```

--------------------------------

### Installing Apache, mod_wsgi, and MySQL on Ubuntu (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

This command installs necessary packages for a production Toaster instance on Ubuntu, including the Apache web server, mod_wsgi for Python integration, MySQL server, and Python pip.

```bash
$ sudo apt install apache2 libapache2-mod-wsgi-py3 mysql-server python3-pip libmysqlclient-dev
```

--------------------------------

### Initialize and Run Poky Build Environment

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

This snippet shows how to set up proxy configurations, navigate to the poky directory, source the build environment initialization script, and start the BitBake Toaster with optional arguments. It concludes with a conditional command to execute a bash script.

```shell
#export http_proxy=http://proxy.host.com:8080
#export https_proxy=http://proxy.host.com:8080
#export GIT_PROXY_COMMAND=$HOME/bin/gitproxy
cd poky/
source ./oe-init-build-env build
source ../bitbake/bin/toaster $1 noweb
[ "$1" == 'start' ] && /bin/bash
```

--------------------------------

### Define Custom QEMU Setup and Cleanup Commands (BitBake Variables)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/migration-guides/release-notes-4.2.rst

These BitBake variables, QB_SETUP_CMD and QB_CLEANUP_CMD, allow the execution of custom shell commands before and after QEMU emulation starts, respectively. This is useful for pre-configuring the environment or performing post-run actions.

```bitbake
QB_SETUP_CMD
```

```bitbake
QB_CLEANUP_CMD
```

--------------------------------

### runqemu Command-Line Usage Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/migration-guides/migration-2.2.rst

Demonstrates how to invoke the runqemu script with specific machine, root filesystem, kernel image, and options. This is a practical example of launching a QEMU instance for testing.

```bash
$ runqemu qemux86-64 tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.ext4 tmp/deploy/images/qemux86-64/bzImage nographic
```

--------------------------------

### Source Buildtools Environment Setup Script (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/system-requirements.rst

Sources the environment setup script to configure the build environment after installing buildtools. This adds the necessary tools to the PATH and initializes other required environment variables.

```shell
$ source /home/your_username/buildtools/environment-setup-x86_64-pokysdk-linux

```

--------------------------------

### Creating Toaster User and Initializing Git Repository (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

These commands create a dedicated 'toaster' user with a specific home directory and then clone the Poky repository into that directory. This prepares the environment for Toaster installation.

```bash
$ sudo /usr/sbin/useradd toaster -md /var/www/toaster -s /bin/false
$ sudo su - toaster -s /bin/bash
$ git clone git://git.yoctoproject.org/poky
$ git checkout &DISTRO_NAME_NO_CAP;
```

--------------------------------

### Install Packages into SDK with devtool

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/extensible.rst

Demonstrates how to install a package into the extensible SDK. The '-s' option allows building from source if the pre-built artifact is not available, though this takes longer.

```bash
$ devtool sdk-install mesa
$ devtool sdk-install -s mesa
```

--------------------------------

### Wic List Images Command Example

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/wic.rst

Command to list available kickstart image configurations provided by Wic. This helps in selecting a pre-defined image type.

```bash
$ wic list images
```

--------------------------------

### Source Buildtools Environment Setup (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/system-requirements.rst

This command sources the environment setup script for the installed buildtools. It adds the build tools to the PATH and initializes necessary environment variables for Git, tar, Python, chrpath, gcc, and make.

```shell
$ source /path/to/poky/buildtools/environment-setup-x86_64-pokysdk-linux
```

--------------------------------

### Create Project Directory for BitBake

Source: https://github.com/yoctoproject/poky/blob/master/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.rst

This snippet demonstrates the initial steps to set up a dedicated directory for a BitBake project. It involves creating a new directory and navigating into it, preparing the workspace for BitBake's metadata and build operations.

```shell
mkdir ~/hello
cd ~/hello
```

--------------------------------

### Apache Configuration for Toaster (Apache Configuration)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

Sample Apache configuration file for serving Toaster. This includes aliasing static files, configuring directory access, and setting up WSGI for the Toaster application.

```apache
Alias /static /var/www/toaster/static_files
<Directory /var/www/toaster/static_files>
   <IfModule mod_access_compat.c>
      Order allow,deny
      Allow from all
   </IfModule>
   <IfModule !mod_access_compat.c>
      Require all granted
   </IfModule>
</Directory>

<Directory /var/www/toaster/poky/bitbake/lib/toaster/toastermain>
   <Files "wsgi.py">
      Require all granted
   </Files>
</Directory>

WSGIDaemonProcess toaster_wsgi python-path=/var/www/toaster/poky/bitbake/lib/toaster:/var/www/toaster/.local/lib/python3.4/site-packages
WSGIScriptAlias / "/var/www/toaster/poky/bitbake/lib/toaster/toastermain/wsgi.py"
<Location />
   WSGIProcessGroup toaster_wsgi
</Location>
```

--------------------------------

### Example SRC_URI for Custom Kernel Recipe

Source: https://github.com/yoctoproject/poky/blob/master/documentation/kernel-dev/common.rst

This example shows how to define the `SRC_URI` variable in a custom kernel recipe. It demonstrates specifying a Git repository and including a `defconfig` file for kernel configuration. Ensure the Git fetcher protocol and configuration file path are correct for your setup.

```bitbake
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;protocol=https;branch=kirkstone-yocto-dev \
           file://defconfig \
           file://my-custom-patch.patch"
LINUX_VERSION = "5.15"
SRCREV = "a1b2c3d4e5f6..."
COMPATIBLE_MACHINE = "qemux86|qemux86-64"
```

--------------------------------

### Run SDK Installer Script

Source: https://github.com/yoctoproject/poky/blob/master/documentation/sdk-manual/appendix-obtain.rst

This command executes a pre-built SDK installer script downloaded from the Yocto Project repository. Ensure the script has execute permissions before running. The installer prompts the user to select the installation directory for the toolchain.

```shell
$ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh
```

--------------------------------

### Get Help for Wic Commands and Topics

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/wic.rst

This snippet demonstrates how to retrieve help information for the 'wic' tool. You can get help for specific commands (like 'write') or general topics (like 'overview', 'plugins', 'kickstart'). This is useful for understanding the functionality and options available for each part of the tool.

```shell
$ wic help command
$ wic help write
$ wic help topic
$ wic help overview
```

--------------------------------

### Suggest Additional Packages for Installation (BitBake)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/variables.rst

Specifies a list of additional packages that can be suggested for installation by the package manager when the main package is installed. Support depends on the package manager.

```bitbake
RSUGGESTS:${PN} = "useful_package another_package"
```

--------------------------------

### Example C Code for Library Version (C)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/prebuilt-libraries.rst

This C code snippet is an example file that might be included in a library's distribution. Its purpose is not explicitly defined in the text, but it's listed under the 'examples' directory for the FT4222H library, suggesting it's a demonstration or utility related to the library's functionality, potentially for checking its version or demonstrating API usage.

```c
// Placeholder for get-version.c content
// The actual code is not provided in the input text.
```

--------------------------------

### PACKAGECONFIG Example with Arguments

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/variables.rst

Illustrates a specific PACKAGECONFIG entry for the 'gtk' feature, showing how to define arguments for enabling and disabling the feature, along with build dependencies. This example demonstrates how to integrate specific build flags and dependencies.

```BitBake
PACKAGECONFIG[gtk] = "--with-gtk3,--without-gtk3,gtk+3"
```

--------------------------------

### Git Fetcher SRC_URI Examples

Source: https://github.com/yoctoproject/poky/blob/master/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst

Examples demonstrating how to use the 'git://' protocol in SRC_URI to fetch source code from Git repositories. These examples showcase different parameter combinations for protocol, branch, and tag.

```bitbake
SRC_URI = "git://github.com/fronteed/icheck.git;protocol=https;branch=${PV};tag=${PV}"
SRC_URI = "git://github.com/asciidoc/asciidoc-py;protocol=https;branch=main"
SRC_URI = "git://git@gitlab.freedesktop.org/mesa/mesa.git;branch=main;protocol=ssh;..."
```

--------------------------------

### Running QEMU with Initramfs Image

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/qemu.rst

This example demonstrates how to configure 'runqemu' to boot using an Initramfs image. This is useful for specific testing or deployment scenarios where an initramfs is preferred over a traditional root filesystem.

```shell
runqemu qemux86-64 core-image-minimal ext4 "BOOT_IMG=bzImage-qemux86-64.bin INITRD=core-image-minimal-qemux86-64-20200218002850.cpio.gz"
```

--------------------------------

### Install Versioned Shared Library (BitBake Recipe)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/prebuilt-libraries.rst

This BitBake recipe installs a versioned shared library, using 'oe_soinstall' to handle the shared library installation and symbolic link creation. It also installs header files and sets up necessary flags to inhibit stripping and symbol splitting for debugging. It's designed for specific architectures and requires license flags.

```bitbake
SUMMARY = "FTDI FT4222H Library"
SECTION = "libs"
LICENSE_FLAGS = "ftdi"
LICENSE = "CLOSED"

COMPATIBLE_HOST = "(i.86|x86_64).*-linux"

# Sources available in a .tgz file in .zip archive
# at https://ftdichip.com/wp-content/uploads/2021/01/libft4222-linux-1.4.4.44.zip
# Found on https://ftdichip.com/software-examples/ft4222h-software-examples/
# Since dealing with this particular type of archive is out of topic here,
# we use a local link.
SRC_URI = "file://libft4222-linux-${PV}.tgz"

S = "${UNPACKDIR}"

ARCH_DIR:x86-64 = "build-x86_64"
ARCH_DIR:i586 = "build-i386"
ARCH_DIR:i686 = "build-i386"

INSANE_SKIP:${PN} = "ldflags"
INHIBIT_PACKAGE_STRIP = "1"
INHIBIT_SYSROOT_STRIP = "1"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"

do_install () {
        install -m 0755 -d ${D}${libdir}
        oe_soinstall ${S}/${ARCH_DIR}/libft4222.so.${PV} ${D}${libdir}
        install -d ${D}${includedir}
        install -m 0755 ${S}/*.h ${D}${includedir}
}
```

--------------------------------

### Post-installation Scripting with pkg_postinst_ontarget()

Source: https://github.com/yoctoproject/poky/blob/master/documentation/migration-guides/migration-2.6.rst

Demonstrates how to defer post-installation scripts to the target's first boot using pkg_postinst_ontarget(). This ensures scripts run on the target system after deployment rather than during root filesystem creation.

```shell
pkg_postinst_ontarget()
{
    # Commands to defer to target first boot
    postinst_intercept delay_to_first_boot
}

pkg_postinst()
{
    # Other post-installation commands if needed
    # ...
    # Call pkg_postinst_ontarget()
    pkg_postinst_ontarget
}

```

--------------------------------

### Example Raspberry Pi Kernel Recipes (BitBake)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/bsp-guide/bsp.rst

This snippet lists example kernel recipes and associated files for the Raspberry Pi BSP. These files, located in the recipes-kernel/linux directory of the Raspberry Pi BSP layer, showcase different kernel versions and configurations. They serve as a reference for creating custom kernel recipes for specific hardware.

```bitbake
files/
linux-raspberrypi_6.12.bb
linux-raspberrypi_6.1.bb
linux-raspberrypi_6.6.bb
linux-raspberrypi-dev.bb
linux-raspberrypi.inc
linux-raspberrypi-v7_6.12.bb
linux-raspberrypi-v7_6.1.bb
linux-raspberrypi-v7_6.6.bb
linux-raspberrypi-v7.inc
```

--------------------------------

### Yocto Project: Example bblayers.conf Configuration

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/structure.rst

Shows a typical structure for the `bblayers.conf` file, which defines the layers BitBake will use. The `BBLAYERS` variable lists the paths to the layers included in the build.

```conf
# Example bblayers.conf content
# LAYERDIR is the root directory of the layer you want to add
BBLAYERS ?= " \
  /path/to/your/meta-poky \
  /path/to/your/meta-openembedded/meta-oe \
  /path/to/your/meta-custom \
  "

```

--------------------------------

### Installing Toaster Python Dependencies (Shell)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/toaster-manual/setup-and-use.rst

This command installs Toaster's Python dependencies using pip3 with the --user flag for isolated installation. It requires being in the Toaster directory and points to the requirements file.

```bash
cd /var/www/toaster/ 
pip3 install --user -r ./poky/bitbake/toaster-requirements.txt
pip3 install --user mysqlclient
```

--------------------------------

### Yocto Recipe: Installing X.Org Configuration Files

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/layers.rst

This BitBake recipe installs X.Org configuration files. It includes logic to conditionally install specific files based on the 'pitft' machine feature. Dependencies include the core BitBake environment and potentially the 'xorg-xserver' package.

```bitbake
SUMMARY = "X.Org X server configuration file"
HOMEPAGE = "http://www.x.org"
SECTION = "x11/base"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

SRC_URI = "file://xorg.conf"

S = "${UNPACKDIR}"

CONFFILES:${PN} = "${sysconfdir}/X11/xorg.conf"

PACKAGE_ARCH = "${MACHINE_ARCH}"
ALLOW_EMPTY:${PN} = "1"

do_install () {
        if test -s ${UNPACKDIR}/xorg.conf; then
                install -d ${D}/${sysconfdir}/X11
                install -m 0644 ${UNPACKDIR}/xorg.conf ${D}/${sysconfdir}/X11/
        fi
}
```

--------------------------------

### Configure INITSCRIPT_PARAMS for update-rc.d

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/variables.rst

The INITSCRIPT_PARAMS variable specifies options passed to the 'update-rc.d' command for managing service initialization scripts. The default value is 'defaults'. Example shows setting runlevels for starting and stopping.

```bitbake
INITSCRIPT_PARAMS = "start 99 5 2 . stop 20 0 1 6 ."
```

--------------------------------

### Build SDK Image with Bitbake

Source: https://github.com/yoctoproject/poky/blob/master/documentation/profile-manual/intro.rst

These commands demonstrate how to build different SDK images using the Bitbake build tool. SDK images include profiling and tracing tools. Ensure you have the Yocto build environment set up.

```bash
bitbake core-image-sato-sdk
bitbake core-image-weston-sdk
bitbake core-image-rt-sdk
```

--------------------------------

### Install Firmware Binary (BitBake)

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/multiconfig.rst

This BitBake task installs the firmware binary into the target root filesystem image. It uses the 'install' command to copy the file specified by 'FIRMWARE_FILE' to the /lib/firmware directory within the destination directory 'D', making it available in the final Linux build.

```bitbake
do_install() {
    install -Dm 0644 ${FIRMWARE_FILE} ${D}/lib/firmware/my-firmware.elf
}
```

--------------------------------

### Manage NFS Share for QEMU

Source: https://github.com/yoctoproject/poky/blob/master/documentation/dev-manual/qemu.rst

These commands manage the NFS share for running QEMU. 'start' initializes the share, 'stop' terminates it, and 'restart' reinitializes it. Replace 'file-system-location' with the actual path to your root filesystem.

```none
runqemu-export-rootfs start file-system-location
```

```none
runqemu-export-rootfs stop file-system-location
```

```none
runqemu-export-rootfs restart file-system-location
```

--------------------------------

### Yocto HTTP/FTP Fetcher Examples

Source: https://github.com/yoctoproject/poky/blob/master/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst

Shows examples of using HTTP, FTP, and HTTPS protocols to fetch files. It includes specifying a download filename and handling authentication with redirection control.

```bitbake
SRC_URI = "http://oe.handhelds.org/not_there.aac"
SRC_URI = "ftp://oe.handhelds.org/not_there_as_well.aac"
SRC_URI = "ftp://you@oe.handhelds.org/home/you/secret.plan"
```

--------------------------------

### Run BitBake Command

Source: https://github.com/yoctoproject/poky/blob/master/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.rst

Executes the BitBake build tool. This command is used to initiate the build process. It requires that configuration files like conf/bitbake.conf exist in the project directory.

```shell
$ bitbake
```

--------------------------------

### Redirect BitBake Errors to Stderr

Source: https://github.com/yoctoproject/poky/blob/master/documentation/migration-guides/migration-1.6.rst

This example illustrates how to capture BitBake errors, which are now output to stderr, by appending '2>&1' to the command line. This is necessary when piping or redirecting the output of the 'bitbake' command.

```Shell
bitbake <your-target> 2>&1
```

--------------------------------

### Run BitBake with Target

Source: https://github.com/yoctoproject/poky/blob/master/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.rst

This command executes the BitBake build process for a specified target, in this case, `printhello`. BitBake parses recipes, resolves dependencies, and executes tasks. Successful execution is indicated by a summary of attempted and succeeded tasks.

```bash
$ bitbake printhello
```

--------------------------------

### Configure BBLAYERS in conf/bblayers.conf

Source: https://github.com/yoctoproject/poky/blob/master/documentation/bsp-guide/bsp.rst

Shows an example of how to configure the BBLAYERS variable in the conf/bblayers.conf file to include various BSP and custom layers. The order of layers matters for build system interpretation.

```bash
BBLAYERS ?= " \
   /usr/local/src/yocto/meta \
   /usr/local/src/yocto/meta-poky \
   /usr/local/src/yocto/meta-yocto-bsp \
   /usr/local/src/yocto/meta-mylayer \
   "

```

--------------------------------

### Run BitBake with Target

Source: https://github.com/yoctoproject/poky/blob/master/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.rst

Builds a specific target recipe using the BitBake command. This command initiates the build process for the 'printhello' recipe after it has been defined and placed within a valid layer.

```shell
$ cd $HOME/hello
$ bitbake printhello
```

--------------------------------

### CMakeLists.txt Example for Systemd Service

Source: https://github.com/yoctoproject/poky/blob/master/documentation/ref-manual/variables.rst

An excerpt from a CMakeLists.txt file that conditionally installs a systemd service based on a build flag. This code snippet is relevant when using PACKAGECONFIG to manage systemd integration in CMake projects.

```CMake
if(WITH_SYSTEMD)
   install(FILES ${PROJECT_SOURCE_DIR}/example.service DESTINATION /etc/systemd/systemd)
endif(WITH_SYSTEMD)
```
Tokens:
Raw