<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts, branch scarthgap-5.0.13</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=scarthgap-5.0.13</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=scarthgap-5.0.13'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-10-13T19:42:58+00:00</updated>
<entry>
<title>scripts/install-buildtools: Update to 5.0.12</title>
<updated>2025-10-13T19:42:58+00:00</updated>
<author>
<name>Aleksandar Nikolic</name>
<email>aleksandar.nikolic@zeiss.com</email>
</author>
<published>2025-10-05T20:05:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9dafc77bd804ca2910d300ad01c13fba83b7dc00'/>
<id>urn:sha1:9dafc77bd804ca2910d300ad01c13fba83b7dc00</id>
<content type='text'>
Update to the 5.0.12 release of the 5.0 series for buildtools

(From OE-Core rev: 2f69dceeebbb67ce06ceda8782a60a71a0ed7f22)

Signed-off-by: Aleksandar Nikolic &lt;aleksandar.nikolic@zeiss.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>runqemu: fix special characters bug</title>
<updated>2025-09-22T20:17:52+00:00</updated>
<author>
<name>Libo Chen</name>
<email>libo.chen.cn@windriver.com</email>
</author>
<published>2025-08-06T02:42:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=54578cd03958c076f6113928fb60f882ada1e107'/>
<id>urn:sha1:54578cd03958c076f6113928fb60f882ada1e107</id>
<content type='text'>
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 &lt;libo.chen.cn@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 3c186fe7741adecb0887e36c8a9164a58fc16437)
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>scripts/install-buildtools: Update to 5.0.11</title>
<updated>2025-08-04T14:55:07+00:00</updated>
<author>
<name>Aleksandar Nikolic</name>
<email>aleksandar.nikolic@zeiss.com</email>
</author>
<published>2025-07-24T19:53:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f6b4415273ae6466e2efc2513be50c71fcabc439'/>
<id>urn:sha1:f6b4415273ae6466e2efc2513be50c71fcabc439</id>
<content type='text'>
Update to the 5.0.11 release of the 5.0 series for buildtools

(From OE-Core rev: 3b3a672ae6c024096cc263a669b1131e3f653b79)

Signed-off-by: Aleksandar Nikolic &lt;aleksandar.nikolic@zeiss.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>oe-debuginfod: add option for data storage</title>
<updated>2025-07-21T16:07:22+00:00</updated>
<author>
<name>Joe Slater</name>
<email>joe.slater@windriver.com</email>
</author>
<published>2025-07-16T09:01:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=792d18b4cb2451b00280641403e6eaf37bd6e53f'/>
<id>urn:sha1:792d18b4cb2451b00280641403e6eaf37bd6e53f</id>
<content type='text'>
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 &lt;joe.slater@windriver.com&gt;
Signed-off-by: Deepesh Varatharajan &lt;Deepesh.Varatharajan@windriver.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>scripts/install-buildtools: Update to 5.0.10</title>
<updated>2025-06-20T15:38:12+00:00</updated>
<author>
<name>Aleksandar Nikolic</name>
<email>aleksandar.nikolic@zeiss.com</email>
</author>
<published>2025-06-13T20:59:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f2648ee38086e8632f319d41008c001b1a2454c0'/>
<id>urn:sha1:f2648ee38086e8632f319d41008c001b1a2454c0</id>
<content type='text'>
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 &lt;aleksandar.nikolic@zeiss.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>scripts/install-buildtools: Update to 5.0.9</title>
<updated>2025-05-19T15:32:49+00:00</updated>
<author>
<name>Aleksandar Nikolic</name>
<email>aleksandar.nikolic@zeiss.com</email>
</author>
<published>2025-05-08T20:16:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=264f11fd980304181a2c59a857862e81689083d2'/>
<id>urn:sha1:264f11fd980304181a2c59a857862e81689083d2</id>
<content type='text'>
Update to the 5.0.9 release of the 5.0 series for buildtools

(From OE-Core rev: 653b2ce8e7b19f668f337cab8726674f595a8dbe)

Signed-off-by: Aleksandar Nikolic &lt;aleksandar.nikolic@zeiss.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>wic: bootimg-efi: Support + symbol in filenames</title>
<updated>2025-04-28T15:18:53+00:00</updated>
<author>
<name>Igor Opaniuk</name>
<email>igor.opaniuk@foundries.io</email>
</author>
<published>2025-04-17T09:11:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8b22b1239b5c84c2e2e6bec14870cbf56f94d570'/>
<id>urn:sha1:8b22b1239b5c84c2e2e6bec14870cbf56f94d570</id>
<content type='text'>
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 &lt;igor.opaniuk@foundries.io&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 3f25822281eb9423ff86105eaebb0bed48663648)
Signed-off-by: Jose Quaresma &lt;jose.quaresma@foundries.io&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>scripts/install-buildtools: Update to 5.0.7</title>
<updated>2025-02-21T14:25:06+00:00</updated>
<author>
<name>Aleksandar Nikolic</name>
<email>aleksandar.nikolic@zeiss.com</email>
</author>
<published>2025-02-16T16:15:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b7eed581007fdb31451e36eb13750bc7d3bb56c4'/>
<id>urn:sha1:b7eed581007fdb31451e36eb13750bc7d3bb56c4</id>
<content type='text'>
Update to the 5.0.7 release of the 5.0 series for buildtools.

(From OE-Core rev: 793d3203db41efa4df1d615db832a771015b7b50)

Signed-off-by: Aleksandar Nikolic &lt;aleksandar.nikolic@zeiss.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>devtool: ide-sdk remove the plugin from eSDK installer</title>
<updated>2025-02-03T14:13:13+00:00</updated>
<author>
<name>Adrian Freihofer</name>
<email>adrian.freihofer@gmail.com</email>
</author>
<published>2025-01-26T12:48:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f997a192d63f2ca6e307b821d2dd76a3e068b29e'/>
<id>urn:sha1:f997a192d63f2ca6e307b821d2dd76a3e068b29e</id>
<content type='text'>
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 &lt;adrian.freihofer@siemens.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>devtool: ide-sdk recommend DEBUG_BUILD</title>
<updated>2025-02-03T14:13:13+00:00</updated>
<author>
<name>Adrian Freihofer</name>
<email>adrian.freihofer@gmail.com</email>
</author>
<published>2025-01-26T12:48:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=04484c6ddec040eb5de7d772dad3d5d89fe9856d'/>
<id>urn:sha1:04484c6ddec040eb5de7d772dad3d5d89fe9856d</id>
<content type='text'>
The debug_build_config function was never called. Compiling with debug
optimized compiler flags was not working. Even with the
--debug-build-config flag set, the build configuration from the recipe
was used.

The devtool ide-sdk --debug-build-config approach didn't work very well
anyway. The problem is that changing the bbappend file doesn't work
while bitbake uses the bbappend file. As a workaround, it would be
possible to parse the recipe, get DEBUG_BUILD and the path to the append
file, exit tinfoil, change the bbappend file, reopen tinfoil and do what
ide-sdk is supposed to do. Such an implementation would be complicated
and slow.
Therefore, the code that was originally supposed to implement this is
removed from ide-sdk and the new --debug-build function of devtool
modify is used instead. Additionally, a hint should be given on how to
manually add DEBUG_BUILD = '1' to bbappend.

This is compatible with the VSCode Bitbake plug-in, which does not
support this parameter anyway.

(From OE-Core rev: 23795962683c792347a17854fb0521734497d4a8)

Signed-off-by: Adrian Freihofer &lt;adrian.freihofer@siemens.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
</feed>
