Wang Mingyu 0c879974c5 autoconf-archive: upgrade 2022.09.03 -> 2023.02.20
Changelog:
==========
  ax_have_qt: bump serial number

  Merge pull request #262 from bastien-roucaries/fromdebian20200930
  Fix  AX_HAVE_QT

  ax_have_qt: bump serial number

  Merge pull request #266 from netfab/fix-ax_have_qt
  AX_HAVE_QT: remove qmake stash file before rmdir

  ax_python_devel: bump serial number

  Merge pull request #267 from bastien-roucaries/fromdebian20221118
  Fix ax_python_devel serial 32 fails with current python3

  ax_add_fortify_source: fix formatting

  ax_check_sign: bump serial number

  ax_cxx_compile_stdcxx: bump serial number

  ax_c_restrict: fix formatting

  Merge pull request #268 from omoerbeek/master
  ax_check_sign: Avoid an unused warning

  Merge pull request #269 from rurban/fortify3
  AX_ADD_FORTIFY_SOURCE: add -D_FORTIFY_SOURCE=3 check

  Merge pull request #270 from rurban/swig
  fix SWIG_LIB windows newline

  Merge pull request #271 from rurban/restrict
  Add ax_c_restrict

  Merge pull request #272 from ojwb/fix-AX_CXX_COMPILE_STDCXX-for-MSVC-C++17
  AX_CXX_COMPILE_STDCXX: Fix MSVC with C++17 or later

  Merge pull request #264 from thesamesam/clang-16
  Clang 16 fixes

(From OE-Core rev: 4aa95afd64ce3cd4caba6f68d6b8aeeea606138a)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-03-06 09:52:16 +00:00
2021-07-19 18:07:21 +01:00

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

The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.

A guide to submitting patches to OpenEmbedded is available at:

https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

There is good documentation on how to write/format patches at:

https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

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

Description
No description provided
Readme 249 MiB