Re: Accessing sbuild build-directory

[Jan Kiszka <jan.kiszka@siemens.com>]

On 28.05.24 09:29, Claudius Heine wrote:
> Hi everyone,
> 
> On 2024-04-05 3:10 pm, 'Scheler, Fabian' via isar-users wrote:
>> Am 05.04.2024 um 12:03 schrieb Scheler, Fabian (T CED EDC-DE):
>>> Am 05.04.2024 um 11:57 schrieb Uladzimir Bely:
>>>> On Fri, 2024-04-05 at 12:09 +0300, Anton Mikanovich wrote:
>>>>> 05/04/2024 11:38, 'Scheler, Fabian (T CED SES-DE)' via isar-users
>>>>> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I want to extract the coverage information (i.e. the gcno-files
>>>>>> created by gcc) that is generated during the package build via
>>>>>> sbuild
>>>>>> and I look for some hook that allows to access the content of the
>>>>>> sbuild build-directory after the build from within a recipe.
>>>>>>
>>>>>> Is this possible?
>>>>>>
>>>>>> Ciao
>>>>>> Fabian
>>>>>
>>>>> Hello Fabian,
>>>>>
>>>>> You can refer to sbuild documentation for hooks explanation.
>>>>> The last one executed inside session before its cleanup is
>>>>> '--chroot-cleanup-commands'.
>>>>> So you can modify dpkg.bbclass adding any custom commands with this
>>>>> hook.
>>>>>
>>>>> There are no already implemented dummy pre/post hooks for now, but we
>>>>> can try to
>>>>> implement them in future if needed.
>>>>>
>>>>
>>>> FWIW, perhaps 6d5fbbab could be used to quickly play with custom hooks
>>>> to sbuild process. A different approach can be chosen for the final
>>>> implementation (if any).
>>>>
>>>
>>> thanks for your quick feedback. Yes, injecting arguments to sbuild like
>>> proposed in 6d5fbbab should be an option. I'll give it a try.
>>
>> FYI: Injecting --post-build-commands finally did the trick, but it is
>> not really nice. However, there seems not to be another option to
>> accomplish that. Unfortunately 6d5fbbab has been reverted and I can
>> follow Jan's arguments, maybe this is a use-case justifying the
>> extension.
> 
> I am currently struggling with a similar issue trying to extract the
> `.config` used to compile the swupdate recipe from cip-core [1].
> 
> Because the debian package uses multiple different build profiles as
> well as a base debian defconfig to generate a `debian_defconfig`, which
> is then used to generate a `.config` it becomes very difficult to verify
> if the configuration I patched into the base debian defconfig has
> actually applied or was overwritten by something else along the way.
> 
> With openembedded you could just look in the build directory and see if
> every option that you wanted is set correctly in the `.config` file, but
> here this is not possible.
> 
> It might be possible to add the `.config` into a binary package and read
> it from there, but there should be an option to investigate the build
> directory in isar itself.
> 

We should add an option to leave the build artifacts behind when leaving
sbuild, just like we had in the ugly old times with buildchroot. I
wanted to study kernel .config and similar stuff in the past more than
once but always found other ad-hoc workarounds to actually solve that
demand properly.

Jan

-- 
Siemens AG, Technology
Linux Expert Center