7f2da28eff
Changelog: ========== API changes: ------------- + Added new function MHD_get_version_bin(). Improvements and enhancements: ------------------------------- * Digest Auth: changed algorithm identifiers in server generated headers from "md5" / "sha-256" to "MD5" / "SHA-256" to better match RFC (while clients should use caseless matching). * Improved Base64 decoding by new implementation with robust input data validation checks. * Improved configure for cross-compiling, for better compatibility with POSIX and for better compatibility with the latest compiler versions. * New internal tests: for Base64 decoding, Basic Auth and folded headers. * Supported new libcurl API in tests to mute deprecation warnings. * Supported ARM and ARM64 for VC compilers. Functionality changes: ------------------------ * any negative number returned by response data generation callback function is treated as an error. Previously negative values except predefined error codes could produce undefined behaviour. * Added handling of "DEBUG" preprocessor macro as an alias of "_DEBUG". Fixes: --------- # Fixed functionality with blocking sockets. # Fixed very inefficient data pumping for upgraded TLS connections. # Fixed processing of folded headers in the requests. # Fixed data races when closing upgraded connection. # Removed duplication of "Connection: upgrade" header. # Digest auth: fixed thread sync to avoid "stale hash" results. # Fixed harmless unwanted extra data processing resulting in triggering of the assert. # Fixed tests for LTO. # Removed removed non-portable functions in examples. # Fixed delayed call of connection notification callback in thread-per-connection mode. # Fixed Address Sanitizer unpoison of memory when memory pool is destroyed. This fixed periodic ASAN error when used for a long time with the sanitizer. # Fixed compiler warnings in library code, examples, tests and configure checks. # New TLS certificates for test-suite: all with SAN fields and SHA-256 hash. # Tests: fixed tests on Darwin 22.x (Ventura). # Tests: redesigned one tests group to avoid stress-testing of the OS. (From OE-Core rev: bdc28b0262ad8a57d56f029b55b338478afb3a07) 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>
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/):
- 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.