Wang Mingyu
2bff1790a0
License-Update: Copyright year updated to 2024 Changelog: =========== - Close the data attribute before reassigning it - Floor division (//) does mathematical division with the floor function applied to the result. - Update new dvrt type and Load Config filed adapt to Windows11 - fix PE.get_data - Fix ambiguous string syntax for PEid parsing regexp - fixed a memory leak that caused the pe file to be access locked. - Exphash from sha256 to md5 to match imphash - More readable calls to superclass - Fix cache_adjust_FileAlignment to work with files not aligned to 0x200 - [StepSecurity] Apply security best practices - Create sets using curly brackets - Change IOError to OSError - Apply isort to sort all imports - Remove "OC Patch" comments - Update tox.ini Python versions - Use with statement to write to file - Remove distutils use - Use chaining comparison operators - Replace list comprehension with set comprehension - Use not in operator - Replace base class name with super() - Increase readability and consistency - Tiny comment improvements - Update oleaut32.py from oleaut32.dll - Improve parse_rich_header - Include ordinals for wsock32.dll - Update ws2_32.py from ws2_32.dll - Update pefile.py for typo - Add parsing for IMAGE_DEBUG_TYPE_EX_DLLCHARACTERISTICS (From OE-Core rev: 5cb8a606874d35f4e22e6ee9691bb3d9d281ce7c) 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.