mirror of https://git.yoctoproject.org/poky synced 2026-02-12 03:33:02 +01:00

Go to file

Bruce Ashfield f35bf272e4 perf: enable zstd in default PACKAGECONFIG

The following upstream commit:

  commit 44b44ffd5dcef03d273ad070d0b02a65a323f5f6
  Author: Leo Yan <leo.yan@arm.com>
  Date:   Sun Dec 15 22:12:22 2024 +0000

      perf build: Minor improvement for linking libzstd

      The zstd library will be automatically linked by detecting the feature
      libzstd.  It is no need to explicitly link it for static builds, so
      remove the redundant linkage.

      It is contradictory to detect the feature libelf-zstd while the build
      configuration NO_LIBZSTD is set.  Report an error for reminding users
      not to set NO_LIBZSTD.

      Signed-off-by: Leo Yan <leo.yan@arm.com>
      Tested-by: Namhyung Kim <namhyung@kernel.org>
      Acked-by: Andrii Nakryiko <andrii@kernel.org>
      Cc: Adrian Hunter <adrian.hunter@intel.com>
      Cc: Alexei Starovoitov <ast@kernel.org>
      Cc: Daniel Borkmann <daniel@iogearbox.net>
      Cc: Eduard Zingerman <eddyz87@gmail.com>
      Cc: Guilherme Amadio <amadio@gentoo.org>
      Cc: Hao Luo <haoluo@google.com>
      Cc: Ian Rogers <irogers@google.com>
      Cc: James Clark <james.clark@linaro.org>
      Cc: Jiri Olsa <jolsa@kernel.org>
      Cc: John Fastabend <john.fastabend@gmail.com>
      Cc: KP Singh <kpsingh@kernel.org>
      Cc: Kan Liang <kan.liang@linux.intel.com>
      Cc: Martin KaFai Lau <martin.lau@linux.dev>
      Cc: Nick Terrell <terrelln@fb.com>
      Cc: Quentin Monnet <qmo@kernel.org>
      Cc: Song Liu <song@kernel.org>
      Cc: Stanislav Fomichev <sdf@google.com>
      Cc: Yonghong Song <yonghong.song@linux.dev>
      Link: https://lore.kernel.org/r/20241215221223.293205-3-leo.yan@arm.com
      Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

Enforces that zstd must be enabled if libelfstd is detected.

Our build of perf and the other default features lead to libelf-zstd
being detected, and hence the build aborts when the features are
checked.

We can't condionally enable this for 6.14+ kernels due to the way that
the perf recipe works. The feature is minor and probably should have
already been in the defaults. To keep things simple, we just enable it
and will watch for any fallout.

(From OE-Core rev: c1b44f4e9f7d13673a93aa81be6a3e11aa9f742b)

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2025-02-27 10:55:17 +00:00

bitbake

bitbake: data_smart: fix indentation

2025-02-25 15:27:28 +00:00

contrib

contrib/git-hooks: add a sendemail-validate example hook that adds FROM: lines to outgoing patch emails

2020-12-30 14:01:07 +00:00

documentation

dev-manual/multiconfig: add suggested best practices and baremetal sections

2025-02-26 14:49:28 +00:00

README.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/):

Git repository: https://git.openembedded.org/openembedded-core/
Mailing list: openembedded-core@lists.openembedded.org

BitBake (files in bitbake/):

Git repository: https://git.openembedded.org/bitbake/
Mailing list: bitbake-devel@lists.openembedded.org

Documentation (files in documentation/):

Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
Mailing list: docs@lists.yoctoproject.org

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

Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
Mailing list: poky@lists.yoctoproject.org

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.