Stefano Babic 53a1911238 libubootenv: upgrade 0.3.2 -> 0.3.3
This includes the following changes:

1081006 Prepare 0.3.3
5d3e33c CMakeLists.txt: fix some inconsistent coding style
0e8f45c fw_printenv: dont hard-code configuration/environment files
44ecc1c fw_setenv: fix bug when SPI flash write size != sector size
9ddccfc uboot_env: fix fileprotect for Android
066bec4 CI: add REUSE compatibility check
5cd7022 Android.bp: add missing copyright
73d0ded Android.bp: initial addition
629c5bc uboot_env: remove unused function
2dab85e uboot_env: remove unused parameters
82730b4 uboot_env: remove unused variables
2736ff3 uboot_env: fix pointer-sign warnings
f5d9292 uboot_env: switch to strchr/strrchr
369121e Add description of the fw_setenv script syntax
10c9a57 Include cstddef in the header for C++
471cdd5 Correct type of conversion of HEX .flags
7dbfffa Fix parsing multiple .flags variables
de31f3d Add REUSE badge
6390c1c Make libubootenv REUSE compliant
0573071 doxygen: fix libuboot_open/close return value description
0d12468 Add documentation for the configuration file
b1178c1 Add configuration for disabling MTD lock
5dadcb3 main: Remove duplicated code about '=' in variable name.
e085e37 libubootenv: Forbid to give empty variable name to fw_setenv.
42f919e main: Check libuboot_set_env() result.
1bc91d1 CI: add gitlab config

(From OE-Core rev: d3f264c62d4759693a9649e7a28e789c8891827f)

Signed-off-by: Stefano Babic <sbabic@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-09-13 10:36:50 +01:00
2022-09-13 10:36:50 +01: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