mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-01-29 21:08:42 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
a738448d83e28e97501ac30076f980efeeab4c83
poky/meta-poky
History
Richard Purdie e83129f4a3 poky-altcfg: Default to ipk packaging 
poky itself defaults to rpm packaging. In support of the binary distro
testing, and for wider testing in general, default poky-altcfg to ipk.

Since we plan to have better "binary distro" testing on the autobuilder
and we plan to primarily use ipk for this, having ipk based images available
as part of our builds is desireable.

Since we want systemd based images with ipk, it makes sense to leave standard
poky using rpm images but switch poky-altcfg to use ipk.

Doing this now for scarthgap gives us a good platform to build off in
the long term too.

This matches https://git.yoctoproject.org/yocto-autobuilder-helper/commit/?id=a9b4f83c05136dd83e07c0f68ae2ad13507ed36a

(From meta-yocto rev: 6d89a66ad8a28d07425cf8886567038950ef65e7)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-03-20 18:21:06 +00:00
..
classes
poky-bleeding: Update and rework
2023-03-21 22:47:01 +00:00
conf
poky-altcfg: Default to ipk packaging
2024-03-20 18:21:06 +00:00
recipes-core
base-files: add usage warning to motd
2024-02-23 14:31:30 +00:00
README.poky.md
README: Clarify/standardise contributions process
2023-09-02 07:46:40 +01:00

README.poky.md

Poky

Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.

Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.

As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.

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

OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.

Contribution Guidelines

Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.

Where to Send Patches

As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:

OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.

CII Best Practices