Poky
Poky is a reference embedded Linux build system and distribution (embedded systems, operating systems) produced by the Yocto Project, combining BitBake and OpenEmbedded metadata to create custom, reproducible Linux images for a wide range of hardware architectures.
- Reference build system and distribution for creating custom embedded Linux images (embedded systems, operating systems).
- Integrates BitBake task executor and OpenEmbedded Core metadata for image and Software Development Kit (SDK) builds (build automation, configuration management).
- Provides a complete toolchain, package feeds, and Board Support Package (BSP) framework for targeted hardware platforms (toolchains, hardware enablement).
- Supports layer-based customization for policies, packages, and machine configurations (configuration management, extensibility framework).
- Serves as the reference implementation and integration baseline for Yocto Project tooling and workflows (embedded build frameworks, DevOps enablement).
More About Poky
Poky is the Yocto Project’s reference embedded Linux build system and reference distribution (embedded systems, operating systems). It addresses the problem of creating reproducible, customizable Linux images for embedded devices across heterogeneous hardware platforms. Instead of providing a fixed general-purpose distribution, Poky supplies the tooling, metadata, and workflows needed to assemble tailored images that match device and product requirements.
At its core, Poky integrates the BitBake build engine (build automation) with OpenEmbedded Core metadata (configuration management) and a set of reference layers. BitBake processes recipes and configuration files to fetch source code, apply patches, configure, compile, and package software. OpenEmbedded Core supplies a maintained collection of recipes, classes, and configuration fragments that define packages, build options, and policies. Poky brings these components together into a coherent build environment with tested configuration defaults, reference machine definitions, and example policies.
Poky provides tooling to generate target images, Software Development Kits (SDKs), and package feeds (toolchains, software distribution). It includes reference Board Support Packages (BSPs) for various architectures and machines (hardware enablement), along with the mechanisms to add custom BSPs. The layer mechanism (extensibility framework) allows organizations to separate vendor, product, and application customizations into modular, composable units. This supports parallel development and controlled integration of features, policies, and hardware support.
In enterprise and institutional environments, Poky is used to build embedded Linux platforms for devices such as networking equipment, industrial controllers, and consumer electronics. Engineering teams use Poky as the base integration environment for their own Yocto Project layers, Continuous Integration (CI) pipelines, and long-term maintenance workflows (DevOps, release engineering). Because Poky is the Yocto Project reference system, documentation, training materials, and many ecosystem layers are aligned with its structure and configuration conventions.
Technically, Poky relies on standard Linux build tools, cross-compilers, and package formats (toolchains, software packaging). It supports multiple Central Processing Unit (CPU) architectures through machine configuration files and BSPs, while distribution configuration files define policies such as initialization system, package formats, and optimization choices. The project’s design focuses on reproducible builds and controlled customization rather than runtime orchestration.
Within a technical directory or taxonomy, Poky fits under embedded Linux build frameworks, embedded operating systems, and DevOps tooling for firmware and device software. It is positioned as the Yocto Project’s integration baseline that organizations extend with their own layers, machine configurations, and product-specific policies to create custom, maintainable embedded Linux platforms.