public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Scheler, Fabian" <Fabian.Scheler@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
	Anton Mikanovich <amikan@ilbers.de>,
	isar-users@googlegroups.com
Subject: Re: Accessing sbuild build-directory
Date: Fri, 5 Apr 2024 12:03:31 +0200	[thread overview]
Message-ID: <4cbee698-bbaf-4d5d-8594-818a93a17f6f@siemens.com> (raw)
In-Reply-To: <b7569ce7fe26989b8108cef8f66baadad825de72.camel@ilbers.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.

Ciao
Fabian
-- 
Siemens AG, Technology

  reply	other threads:[~2024-04-05 10:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  8:38 Scheler, Fabian (T CED SES-DE)
2024-04-05  9:09 ` Anton Mikanovich
2024-04-05  9:57   ` Uladzimir Bely
2024-04-05 10:03     ` Scheler, Fabian [this message]
2024-04-05 13:10       ` Scheler, Fabian
2024-05-28  7:29         ` Claudius Heine
2024-05-28  7:58           ` Jan Kiszka
2024-05-28  8:49             ` Claudius Heine
2024-05-28  8:52               ` Jan Kiszka
2024-05-29 11:24                 ` Anton Mikanovich
2024-05-29 12:33                   ` Jan Kiszka
2024-05-29 12:54                     ` Baurzhan Ismagulov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4cbee698-bbaf-4d5d-8594-818a93a17f6f@siemens.com \
    --to=fabian.scheler@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox