Wang Mingyu
4564b777ff
Changelog:
==========
-Add -T workaround for GNU ld 2.36
-Add extern "C" to headers for easier use by C++
-Avoid format error on i686
-Fix the -march issue for riscv64
-Fix musl build
-Fix invalid free in main()
-Remove deprecated --add-needed linker flag
-src/Makefile: build util.c separately for makeguids
-Adjust dependency for libefivar and libefiboot objects
-Set LC_ALL=C to force English output from ld
-LLD: fix detection and remove not needed workarounds
-Fix glibc 2.36 build (mount.h conflicts)
-File device paths: don't print "File(" or ")"
-Use off_t instead of off64_t
-Revamp efi_well_known_* variable handling
-Allow overriding PKG_CONFIG
-Allow passing of hex values to -A
-Allow -a to create a non-existent variable
-make: add option to disable building/installing the docs
-esl-iter.h: fix type declaration of return value for gcc-13
-Minor code updates
-src/Makefile: do not override LIBS and CFLAGS for prerequisites
-linux: handle non-ACPI systems in device_get()
-Change set&append data to be const.
-dp.h: check _ucs2size in format_ucs2()
-Fix wrong if condition in efi_variable_get_data
-Make README statement match license
-Remove needless access() in efivarfs_probe()
(From OE-Core rev: d8fdd64d13d5598b16ddf7329d5ca283ec7da518)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.