Yocto Project

https://docs.yoctoproject.org/5.0.11/
Admin
Yocto Project is a Linux Foundation collaborative project that provides tools and metadata for...
Tokens:868,078
Snippets:12,403
Trust Score:10
Update:5 months ago
Show doc for...
Tokens:
Raw
### Example Yocto Project SDK Installer Filename

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/using

Provides a concrete example of an SDK installer filename, illustrating the application of the naming convention for a specific configuration (64-bit host, i586 target, core-image-sato, DISTRO snapshot).

```text
poky-glibc-x86_64-core-image-sato-i586-toolchain-DISTRO.sh
```

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

### Example Yocto Project SDK Installer

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/appendix-obtain

Provides a concrete example of a Yocto Project SDK installer filename for a 64-bit x86 build host needing an extended SDK for a 64-bit core2 QEMU target. This aids in understanding the convention in practice.

```bash
poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-5.0.11.sh
```

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

### SDK Installer Example - Bash

Source: https://docs.yoctoproject.org/5.0.11/_sources/sdk-manual/using

This example demonstrates how to execute the Yocto Project Standard SDK installer script. It shows the command to run the installer from a specific directory and the interactive prompts during the installation process, including setting the target installation directory and confirming the installation.

```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
```

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

### Running the Yocto Project SDK Installer (Shell)

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/using

Demonstrates the command to execute the Yocto Project SDK installer script from the command line. This includes specifying the path to the installer and interacting with the installer prompts for directory selection and confirmation.

```shell
$ ./Downloads/poky-glibc-x86_64-core-image-sato-i586-toolchain-5.0.11.sh
Poky (Yocto Project Reference Distro) SDK installer version 5.0.11
===============================================================
Enter target directory for SDK (default: /opt/poky/5.0.11):
You are about to install the SDK to "/opt/poky/5.0.11". 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/5.0.11/environment-setup-i586-poky-linux
```

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

### Example Yocto SDK Installer Filename

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/extensible

Provides a concrete example of an SDK installer script name, illustrating the structure described in the filename convention. This example is for a 64-bit development host and an i586-tuned target architecture.

```text
poky-glibc-x86_64-core-image-sato-i586-toolchain-ext-5.0.11.sh
```

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

### Run Yocto Project SDK Installer

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/appendix-obtain

Executes the generated SDK installer script. Navigate to the SDK deployment directory (`tmp/deploy/sdk`) within your build directory and run the installer script. This script will guide you through choosing the installation root location for the toolchain.

```bash
$ cd poky/build/tmp/deploy/sdk
$ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-5.0.11.sh

```

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

### Initialize Yocto Project Build Environment

Source: https://docs.yoctoproject.org/5.0.11/brief-yoctoprojectqs/index

This command runs the environment setup script for Yocto Project's build system. It creates necessary configuration files (local.conf and bblayers.conf) and sets up environment variables required for building an image. It is crucial for starting the build process.

```bash
$ cd poky
$ source oe-init-build-env
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, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

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

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

For more information about OpenEmbedded see their website:
    https://www.openembedded.org/
```

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

### Running the Yocto Extensible SDK Installer

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/extensible

Demonstrates how to execute the Yocto Project Extensible SDK installer script from the command line. This example assumes the installer is in the Downloads directory and has execute permissions.

```bash
$ ./Downloads/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.5.sh
Poky (Yocto Project Reference Distro) Extensible SDK installer version 2.5
==========================================================================
Enter target directory for SDK (default: poky_sdk):
You are about to install the SDK to "/home/scottrif/poky_sdk". Proceed [Y/n]? Y
Extracting SDK..............done
Setting it up...
Extracting buildtools...
Preparing build system...
Parsing recipes: 100% |##################################################################| Time: 0:00:52
Initialising tasks: 100% |###############################################################| Time: 0:00:00
Checking sstate mirror object availability: 100% |#######################################| Time: 0:00:00
Loading cache: 100% |####################################################################| Time: 0:00:00
Initialising tasks: 100% |###############################################################| Time: 0:00:00
done
SDK has been successfully set up and is ready to be used.
```

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

### Executing a Yocto Project SDK Installer

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/appendix-obtain

Demonstrates how to execute a downloaded Yocto Project SDK installer script from the Downloads directory, assuming the user has obtained the correct installer file. This is a practical step for installing the SDK.

```bash
$ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-5.0.11.sh
```

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

### Example BitBake Install Function

Source: https://docs.yoctoproject.org/5.0.11/_sources/dev-manual/new-recipe

Provides an example of a 'do_install' function in a BitBake recipe, demonstrating how to create directories, move binaries, and remove unnecessary directories.

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

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

### Sourcing the Yocto Project SDK Environment Setup Script (Shell)

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/using

Shows the command to source the SDK environment setup script, which is necessary to activate the SDK in a new shell session. This command configures the necessary environment variables for using the SDK tools.

```shell
$ source /opt/poky/5.0.11/environment-setup-i586-poky-linux
```

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

### Run SDK Installer Script

Source: https://docs.yoctoproject.org/5.0.11/_sources/sdk-manual/appendix-obtain

Command to execute the SDK installer script located in the 'tmp/deploy/sdk' directory of your build environment. The script guides the user through choosing the installation path for the toolchain.

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

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

### Get Overview Help for `wic`

Source: https://docs.yoctoproject.org/5.0.11/dev-manual/wic

Provides an example of retrieving overview help for the `wic` command. This is a specific instance of getting help for a topic.

```shell
$ wic help overview
```

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

### Yocto Project SDK Installer Filename Convention

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/appendix-obtain

Illustrates the naming convention for Yocto Project SDK installer files, specifying the components like host system, image type, target architecture, and release version. This helps users identify the correct installer for their needs.

```text
poky-glibc-host_system-core-image-type-arch-toolchain[-ext]-release.sh
```

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

### Initialize Cross-Development Environment with Bash

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/appendix-obtain

This command initializes the cross-development environment by sourcing the setup script. It sets up necessary environment variables for subsequent operations. The script's location depends on where the toolchain was installed.

```bash
$ source poky_sdk/environment-setup-core2-64-poky-linux

```

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

### Start Toaster for Local Development (Shell)

Source: https://docs.yoctoproject.org/5.0.11/toaster-manual/setup-and-use

This snippet shows the basic commands to navigate to the source directory, source the build environment, and start the Toaster service for local development. It assumes Yocto Project and Toaster dependencies are already installed.

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

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

### Python3targetconfig Class Usage Example

Source: https://docs.yoctoproject.org/5.0.11/_sources/migration-guides/migration-3.3

Illustrates how to change recipes to inherit the new python3targetconfig class instead of python3native when target configuration data is needed. This ensures correct installation directories and adds a dependency on target python3.

```python
inherit python3targetconfig

# Previously:
# inherit python3native

# Example recipes affected: gpgme, libcap-ng, python3-pycairo
```

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

### Run QEMU Script Examples

Source: https://docs.yoctoproject.org/5.0.11/_sources/dev-manual/qemu

A collection of examples illustrating the usage of the 'runqemu' script for various emulation scenarios. These examples showcase how to specify machine types, image paths, boot parameters, and other QEMU-specific options.

```shell
$ runqemu

```

```shell
$ runqemu qemuarm

```

```shell
$ runqemu tmp/deploy/images/qemuarm

```

```shell
$ runqemu tmp/deploy/images/qemux86/qemuboot.conf

```

```shell
$ runqemu qemux86-64 core-image-sato ext4

```

```shell
$ runqemu qemux86-64 wic-image-minimal wic

```

```shell
$ runqemu path/to/bzImage-qemux86.bin path/to/nfsrootdir/ serial

```

```shell
$ runqemu qemux86 iso/hddimg/wic.vmdk/wic.qcow2/wic.vdi/ramfs/cpio.gz...

```

```shell
$ runqemu qemux86 qemuparams="-m 256"

```

```shell
$ runqemu qemux86 bootparams="psplash=false"

```

```shell
$ runqemu path/to/<image>-<machine>.wic

```

```shell
$ runqemu path/to/<image>-<machine>.wic.vmdk

```

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

### Start Toaster for Local Development

Source: https://docs.yoctoproject.org/5.0.11/_sources/toaster-manual/setup-and-use

This command initiates the Toaster web interface for local development. Ensure the build environment is sourced beforehand. Toaster will be accessible via a web browser at the default address http://127.0.0.1:8000.

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

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

### Example C code for getting library version (C)

Source: https://docs.yoctoproject.org/5.0.11/_sources/dev-manual/prebuilt-libraries

This C code snippet is an example of how to get the version of a pre-built library. It is typically used in conjunction with libraries that expose version information through specific functions or symbols.

```c
// get-version.c
// Example of how to get the version of a library

#include <stdio.h>
#include "libft4222.h" // Assuming this header file is available

int main() {
    // Assuming a function like FT_GetLibraryVersion exists and returns a value that can be printed
    // The actual function and return type would depend on the specific library (libft4222 in this case).
    // For demonstration, let's assume a hypothetical function call:
    // unsigned int version = FT_GetLibraryVersion(); 
    // printf("Library Version: %u\n", version);
    
    // Placeholder for actual version retrieval logic
    printf("Placeholder for getting library version.\n");
    printf("Actual implementation depends on libft4222 API.\n");
    
    return 0;
}
```

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

### Starting Toaster Django Web Server (Shell)

Source: https://docs.yoctoproject.org/5.0.11/_sources/toaster-manual/setup-and-use

Shell commands to initialize the build environment and start the Toaster Django web server. This allows for testing the database integration.

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

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

### Start Toaster Django Development Server

Source: https://docs.yoctoproject.org/5.0.11/toaster-manual/setup-and-use

This command sequence initializes the Yocto Project build environment and then starts the Toaster Django development web server. This allows for testing and initial use of Toaster with its configured MySQL database.

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

```

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

### Install Custom CMake Toolchain Files

Source: https://docs.yoctoproject.org/5.0.11/_sources/ref-manual/classes

This example demonstrates how to install custom CMake toolchain files provided by an application. These files should be installed to the preferred CMake Module directory during the 'install' task.

```bash
install -d 	"${D}${datadir}/cmake/modules/"
install -m 0644	${S}/cmake/MyToolchain.cmake \
			"${D}${datadir}/cmake/modules/"
```

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

### SDK Information File Example

Source: https://docs.yoctoproject.org/5.0.11/dev-manual/build-quality

An example of the `sdk-info.txt` file, which contains name-value pairs detailing the SDK's configuration and characteristics. This file is crucial for understanding the SDK's composition and potential influences on its content.

```shell
DISTRO = poky
DISTRO_VERSION = 1.3+snapshot-20130327
SDK_NAME = poky-glibc-i686-arm
SDK_VERSION = 1.3+snapshot
SDKMACHINE =
SDKIMAGE_FEATURES = dev-pkgs dbg-pkgs
BAD_RECOMMENDATIONS =
SDKSIZE = 352712

```

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

### Yocto Project SDK Installer Filename Convention

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/using

Explains the structure of the Yocto Project SDK installer filenames. This convention helps users identify the correct installer based on host system, image type, target architecture, and release version.

```text
poky-glibc-host_system-image_type-arch-toolchain-release_version.sh

Where:
    host_system is a string representing your development system: i686 or x86_64.
    image_type is the image for which the SDK was built: core-image-minimal or core-image-sato.
    arch is a string representing the tuned target architecture: aarch64, armv5e, core2-64, i586, mips32r2, mips64, ppc7400, or cortexa8hf-neon.
    release_version is a string representing the release number of the Yocto Project: 5.0.11, 5.0.11+snapshot
```

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

### Install Apache and Dependencies on openSUSE

Source: https://docs.yoctoproject.org/5.0.11/_sources/toaster-manual/setup-and-use

Installs Apache webserver, mod_wsgi for Python 3, Python 3 pip, MariaDB server, and development libraries needed for a production Toaster instance on openSUSE systems.

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

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

### Copy and Execute Instrumented 'hello world' with LTTng

Source: https://docs.yoctoproject.org/5.0.11/_sources/profile-manual/usage

This snippet demonstrates how to copy an instrumented 'hello world' executable to a target machine, connect via SSH, create an LTTng trace session, enable user-space events, start tracing, run the program, stop tracing, and view the trace output. It assumes the 'hello' executable is already built and available.

```bash
$ cd build/tmp/work/core2_32-poky-linux/lttng-ust/2.0.5-r0/git/tests/hello/.libs
$ scp hello root@192.168.1.20:
$ ssh -l root 192.168.1.47
root@crownbay:~# lttng create
root@crownbay:~# lttng enable-event --userspace --all
root@crownbay:~# lttng start
root@crownbay:~# ./hello
root@crownbay:~# lttng stop
root@crownbay:~# lttng view
root@crownbay:~# lttng destroy
```

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

### Source buildtools Environment Setup (Shell)

Source: https://docs.yoctoproject.org/5.0.11/_sources/ref-manual/system-requirements

Command to source the environment setup script after installing the buildtools. This action adds the installed tools to the PATH and initializes other necessary environment variables, making Git, tar, Python, chrpath, and potentially gcc and make available for use.

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

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

### Configure Minimal Extensible SDK Installer (Configuration)

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/appendix-customizing

Sets the Extensible SDK to a minimal type, significantly reducing the installer size. This requires manual installation of libraries and tools after the initial setup.

```configuration
SDK_EXT_TYPE = "minimal"

```

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

### Class Override Example for Target Builds

Source: https://docs.yoctoproject.org/5.0.11/_sources/ref-manual/variables

An example demonstrating how CLASSOVERRIDE can be used to apply specific configurations, such as installing extra files, only when building for the target architecture.

```Bitbake
CLASSOVERRIDE = "class-target"

```

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

### Simulate Image with QEMU

Source: https://docs.yoctoproject.org/5.0.11/_sources/brief-yoctoprojectqs/index

Starts a QEMU (Quick EMUlator) session to simulate the built OS image. QEMU is included with the Yocto Project and allows for testing images without physical hardware. This command requires a previously built image.

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

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

### Initscript Parameters: INITSCRIPT_PARAMS Example

Source: https://docs.yoctoproject.org/5.0.11/_sources/ref-manual/variables

Specifies options passed to the 'update-rc.d' command for managing initialization scripts. This example shows runlevel configurations for starting and stopping scripts.

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

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

### Install Apache and Dependencies on Ubuntu

Source: https://docs.yoctoproject.org/5.0.11/_sources/toaster-manual/setup-and-use

Installs Apache webserver, mod-wsgi, MySQL server, and Python 3 related packages required for a production Toaster instance on Ubuntu systems.

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

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

### Get Help for Wic Topics

Source: https://docs.yoctoproject.org/5.0.11/_sources/dev-manual/wic

This command allows users to access help on predefined topics within Wic, including 'overview', 'plugins', and 'kickstart'. This is useful for understanding the broader concepts and structure of Wic.

```bash
$ wic help topic
```

```bash
$ wic help overview
```

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

### Define Complementary Package Globbing in Yocto

Source: https://docs.yoctoproject.org/5.0.11/ref-manual/variables

Defines wildcards for installing complementary packages for all installed packages in an image. This uses Unix filename pattern matching and is associated with IMAGE_FEATURES. The example shows how to define a 'dev-pkgs' feature to install all '-dev' packages.

```BitBake
COMPLEMENTARY_GLOB[dev-pkgs] = '*-dev'

```

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

### Start Multi-Host PR Service via Command Line

Source: https://docs.yoctoproject.org/5.0.11/_sources/dev-manual/packages

Starts the PR Service for a multi-host setup where multiple development systems share a common package feed. The service is started using the 'bitbake-prserv' command with specified host and port.

```bash
bitbake-prserv --host ip --port port --start
```

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

### Get Help for `wic` Topics

Source: https://docs.yoctoproject.org/5.0.11/dev-manual/wic

Illustrates how to access help documentation for predefined topics within `wic`, such as 'overview' and 'plugins'. This provides in-depth information on specific aspects of the `wic` tool.

```shell
$ wic help topic
```

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

### Build and Deploy CMake Example Project with Yocto

Source: https://docs.yoctoproject.org/5.0.11/_sources/sdk-manual/extensible

This snippet demonstrates the workflow for modifying a CMake example project, building it, installing firmware on a target device or QEMU, and running unit tests. It utilizes devtool, runqemu, and CMake commands for compilation and testing.

```sh
# Create the SDK
devtool modify cmake-example --debug-build
devtool ide-sdk cmake-example core-image-minimal -c --ide=none

# Install the firmware on a target device or start QEMU
runqemu

# From exploring the workspace of cmake-example
cd build/workspace/sources/cmake-example

# Find cmake-native and save the path into a variable
# Note: using just cmake instead of $CMAKE_NATIVE would work in many cases
CMAKE_NATIVE="$(jq -r '.configurePresets[0] | "\(.cmakeExecutable)"' CMakeUserPresets.json)"

# List available CMake presets
"$CMAKE_NATIVE" --list-presets
Available configure presets:

  "cmake-example-cortexa57" - cmake-example: cortexa57

# Re-compile the already compiled sources
"$CMAKE_NATIVE" --build --preset cmake-example-cortexa57
ninja: no work to do.
# Do a clean re-build
"$CMAKE_NATIVE" --build --preset cmake-example-cortexa57 --target clean
[1/1] Cleaning all built files...
Cleaning... 8 files.
"$CMAKE_NATIVE" --build --preset cmake-example-cortexa57 --target all
[7/7] Linking CXX executable cmake-example

# Run the cross-compiled unit tests with QEMU user-mode
"$CMAKE_NATIVE" --build --preset cmake-example-cortexa57 --target test
[0/1] Running tests...
Test project .../build/tmp/work/cortexa57-poky-linux/cmake-example/1.0/cmake-example-1.0
    Start 1: test-cmake-example
1/1 Test #1: test-cmake-example ...............   Passed    0.03 sec

100% tests passed, 0 tests failed out of 1

Total Test time (real) =   0.03 sec

# Using CTest directly is possible as well
CTEST_NATIVE="$(dirname "$CMAKE_NATIVE")/ctest"

# List available CMake presets
"$CTEST_NATIVE" --list-presets
Available test presets:

  "cmake-example-cortexa57" - cmake-example: cortexa57

# Run the cross-compiled unit tests with QEMU user-mode
"$CTEST_NATIVE" --preset "cmake-example-cortexa57"
Test project ...build/tmp/work/cortexa57-poky-linux/cmake-example/1.0/cmake-example-1.0
    Start 1: test-cmake-example
1/1 Test #1: test-cmake-example ...............   Passed    0.03 sec

100% tests passed, 0 tests failed out of 1

Total Test time (real) =   0.03 sec

# Deploying the new build to the target device (default is QEUM at 192.168.7.2)
oe-scripts/install_and_deploy_cmake-example-cortexa57

# Start a remote debugging session with gdbserver on the target and GDB on the host
oe-scripts/gdbserver_1234_usr-bin-cmake-example_m
oe-scripts/gdb_1234_usr-bin-cmake-example
break main
run
step
stepi
continue
quit

# Stop gdbserver on the target device
oe-scripts/gdbserver_1234_usr-bin-cmake-example_m stop

```

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

### Execute 'hello' Project on Target Hardware

Source: https://docs.yoctoproject.org/5.0.11/_sources/sdk-manual/working-projects

This command executes the 'hello' project on the target hardware, assuming the build host is the target. It demonstrates a basic project execution flow by printing 'Hello World!'.

```shell
$ ./tmp/usr/local/bin/hello
```

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

### Install Packages in Core Image Initramfs Boot

Source: https://docs.yoctoproject.org/5.0.11/ref-manual/variables

This example shows how to define the packages to be installed in the core-image-initramfs-boot image. It includes initramfs scripts, the virtual runtime base-utils, and base-passwd.

```bitbake
PACKAGE_INSTALL = "${INITRAMFS_SCRIPTS} ${VIRTUAL-RUNTIME_base-utils} base-passwd"

```

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

### QEMU Help Output for runqemu

Source: https://docs.yoctoproject.org/5.0.11/_sources/dev-manual/qemu

Displays the command-line help output for the 'runqemu' script, detailing available environment variables and simplified QEMU options. This output guides users on how to configure kernel, rootfs, machine, and various QEMU features like graphics, networking, and security.

```shell
$ runqemu --help

Usage: you can run this script with any valid combination
of the following environment variables (in any order):
  KERNEL - the kernel image file to use
  ROOTFS - the rootfs image file or nfsroot directory to use
  MACHINE - the machine name (optional, autodetected from KERNEL filename if unspecified)
  Simplified QEMU command-line options can be passed with:
    nographic - disable video console
    serial - enable a serial console on /dev/ttyS0
    slirp - enable user networking, no root privileges required
    kvm - enable KVM when running x86/x86_64 (VT-capable CPU required)
    kvm-vhost - enable KVM with vhost when running x86/x86_64 (VT-capable CPU required)
    publicvnc - enable a VNC server open to all hosts
    audio - enable audio
    [*/]ovmf* - OVMF firmware file or base name for booting with UEFI
    tcpserial=<port> - specify tcp serial port number
    biosdir=<dir> - specify custom bios dir
    biosfilename=<filename> - specify bios filename
    qemuparams=<xyz> - specify custom parameters to QEMU
    bootparams=<xyz> - specify custom kernel parameters during boot
    help, -h, --help: print this text

```

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

### Setting SDK Installer Title

Source: https://docs.yoctoproject.org/5.0.11/ref-manual/variables

Specifies the title displayed when the SDK installer is run. By default, it's derived from DISTRO_NAME or DISTRO. This example shows how to set a custom title.

```bitbake
SDK_TITLE ??= "${@d.getVar('DISTRO_NAME') or d.getVar('DISTRO')} SDK"
# Example for Poky:
# SDK_TITLE = "Poky (Yocto Project Reference Distro) SDK"
```

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

### Build Yocto Project Extensible SDK Installer

Source: https://docs.yoctoproject.org/5.0.11/sdk-manual/appendix-obtain

Builds the SDK installer for an extensible SDK. Similar to the standard SDK build, replace 'image' with your target image name. This command also produces an SDK installer with a sysroot matching your target root filesystem.

```bash
$ bitbake image -c populate_sdk_ext

```

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

### Create 'Hello World!' Module Header File

Source: https://docs.yoctoproject.org/5.0.11/_sources/sdk-manual/working-projects

This C header file declares the 'sample_func' function and includes the standard input/output library. It serves as an interface for the 'main.c' file.

```c
#include <stdio.h>
void sample_func();
```
Tokens:
Raw