linux/poky.git/scripts, branch yocto-5.0.14

oe-build-perf-report: relax metadata matching rules

2025-11-18T00:59:28+00:00

As the poky repository is no longer used, measurements are indexed using the oe-core commit. But as bitbake, oe-core and meta-yocto are now retrieved from separate gits, while measuring performances for a given branch at some time interval, we can get the same commit for oe-core but different ones for bitbake or meta-yocto. As a consequence, metadata associated with the same index (oe-core commit) might differ. To work around this, relax the equality checks for commit, commit_time and commit_count since they might no longer match. Ideally we'd group them into separate results but for now, treat them as being the same. [Based on work from Mathieu Dubois-Briand but fixed differently] (From OE-Core rev: d9c30edf908c129a7540b23e920dd669d2a30657) Signed-off-by: Richard Purdie (cherry picked from commit e7dc42e30c76bf0fbb4d3cc019bbec675bac55fa) Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 5.0.12

2025-10-13T19:42:58+00:00

Update to the 5.0.12 release of the 5.0 series for buildtools (From OE-Core rev: 2f69dceeebbb67ce06ceda8782a60a71a0ed7f22) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

runqemu: fix special characters bug

2025-09-22T20:17:52+00:00

Fix the bug in runqemu that happens when the file path contains the specific words such as 'vmlinux', e.g. /home/frank/vmlinux. runqemu - ERROR - wic doesn't need kernel (From OE-Core rev: 0276bd0e8d5cefb6f98d685bc9faa0451780bef9) Signed-off-by: Libo Chen Signed-off-by: Richard Purdie (cherry picked from commit 3c186fe7741adecb0887e36c8a9164a58fc16437) Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 5.0.11

2025-08-04T14:55:07+00:00

Update to the 5.0.11 release of the 5.0 series for buildtools (From OE-Core rev: 3b3a672ae6c024096cc263a669b1131e3f653b79) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

oe-debuginfod: add option for data storage

2025-07-21T16:07:22+00:00

Storing the data files under $HOME can be unreliable if debuginfod is used for several projects, especially if $HOME is shared between machines. We provide an option to save files under the project directory. The default behavior is unchanged. (From OE-Core rev: e1e0cf82f559077e2a51447baf137086202c0c4a) (From OE-Core rev: 24c0ab18045920bb5c1e965c0ea6d176fd6de234) Signed-off-by: Joe Slater Signed-off-by: Deepesh Varatharajan Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 5.0.10

2025-06-20T15:38:12+00:00

Update to the 5.0.10 release of the 5.0.10 series for buildtools (From OE-Core rev: 6c3344ba51a42252e347db2f6013c49d35413ea0) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 5.0.9

2025-05-19T15:32:49+00:00

Update to the 5.0.9 release of the 5.0 series for buildtools (From OE-Core rev: 653b2ce8e7b19f668f337cab8726674f595a8dbe) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

wic: bootimg-efi: Support + symbol in filenames

2025-04-28T15:18:53+00:00

Allow the '+' symbol as a valid character in filenames listed in the IMAGE_EFI_BOOT_FILES variable. The '+' symbol might be used to support boot counting for boot entries, as described in the UAPI Boot Loader Specification [1]: The boot counting data is stored in the name of the boot loader entry. A boot loader entry file name may contain a plus (+) followed by a number. This may optionally be followed by a minus (-) followed by a second number. The dot (.) and file name suffix (conf or efi) must immediately follow. Boot counting is enabled for entries which match this pattern. Example: IMAGE_EFI_BOOT_FILES:append = " entry.conf;loader/entries/entry+3.conf" [1] https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting (From OE-Core rev: 081fa0ebb33dbbfd0f6e8239690261c0a9dcdb2c) Signed-off-by: Igor Opaniuk Signed-off-by: Richard Purdie (cherry picked from commit 3f25822281eb9423ff86105eaebb0bed48663648) Signed-off-by: Jose Quaresma Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 5.0.7

2025-02-21T14:25:06+00:00

Update to the 5.0.7 release of the 5.0 series for buildtools. (From OE-Core rev: 793d3203db41efa4df1d615db832a771015b7b50) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

devtool: ide-sdk remove the plugin from eSDK installer

2025-02-03T14:13:13+00:00

The ide-sdk command bootstraps the SDK from the bitbake environment before the IDE configuration is generated. In the case of the eSDK installer, the bootstrapping is performed during the installation of the eSDK installer. Running the ide-sdk plugin from an eSDK installer based setup would require skipping the bootstrapping and probably taking some other differences into account when generating the IDE configurations. This would be possible. But it will probably never be implemented, as running devtool ide-sdk directly from the bitbake environment is much more flexible. Also, some of the recent improvements that have made it into the core have the potential to make the eSDK installer obsolete at some point in the future: - bitbake-layers create-layers-setup replicates the layers - bitbake-config-build replicates the build configuration - The new sstate mirror features replicate the sstate - bblock locks the sstate more flexible than the eSDK installer - devtool ide-sdk bootstraps the SDK directly from the bitbake environment. The same environment-setup... file is provided with --mode=shared. The devtool modify based workflow is supported since always by devtool and also the default --mode of devtool ide-sdk. These functions essentially cover what the eSDK installer does without a need for the current implementation of the eSDK installer and the populate_sdk_ext, which is hard to maintain and takes a lot of time to build. This means that instead of making the ide-sdk plugin compatible with the eSDK installer, we should rather replace the current implementation of the eSDK installer and populate_sdk_ext with an implementation that can replicate a normal bitbake environment in a convenient way where the ide-sdk plugin also just works without additional complexity. (From OE-Core rev: f50306ea3e174b8db46b20b68a7ac4299a69f50d) Signed-off-by: Adrian Freihofer Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman