Deepesh Varatharajan a450fa44a8 binutils: stable 2.45 branch updates
Below commits on binutils-2.45 stable branch are updated.

316da476e61 visium MAX_MEM_FOR_RS_ALIGN_CODE
b58f54a9bde strip: Don't treat fat IiR objects as plugin object
a71a4df76e2 strip: Treat "default" output_target as unspecified
96114b5c147 strip: Don't check target_defaulted in input BFD
2b2e51a31ec libctf: link: rejig lazy opening to not need weak symbols
ae8c1b4241a libctf: don't run tests requiring deduplicating linker unless one is in use
e54a1de9515 libctf: exclude always-emitted Solaris symbols from the symtypetab
32830073ea0 libctf: get libctf-nobfd.ver from the right place with Solaris ld
404cb58a92f libctf: do not use mmap on Solaris 11
99f48156dd1 LoongArch: Fix symbol size after relaxation
d45e8bff0b4 libiberty: sync with gcc
b09f71c1c46 Re: resbin: don't pass NULL as printf %s arg
72d7cfff264 PR 33229 nds32 gas segfaults on gcc output
879eabba0fc Fix more unused variable warnings
29996106c19 Fix unused variable warnings
5541a7e7712 binutils: drop unused note_size, contents, old variables
f4290b25097 bfd: drop unused elt_no
2a07e06e269 Re: Re-enable development on the 2.45 branch
ad8cf343ab5 Re-enable development on the 2.45 branch

Test Results:
                                 Before  After  Diff
No. of expected passes            315     317    +2
No. of unexpected failures        1       1      0
No. of untested testcases         1       1      0
No. of unsupported tests          9       9      0

96114b5c147 strip: Don't check target_defaulted in input BFD
The above commit adds the newly passing test cases.

PASSed tests changes
+PASS: binutils-all/x86-64/pr33230.obj ( --strip-debug)
+PASS: binutils-all/x86-64/pr33230.obj (--input-target=default --strip-debug)

(From OE-Core rev: 324f75bffa95a1b97048032f9bdaf0ff7d770f7a)

Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2025-09-15 17:57:23 +01:00
2025-09-15 17:57:23 +01:00
2024-02-19 11:34:33 +00: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

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

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