public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Scheler, Fabian (T CED SES-DE)" <Fabian.Scheler@siemens.com>
To: isar-users@googlegroups.com
Subject: Accessing sbuild build-directory
Date: Fri, 5 Apr 2024 10:38:42 +0200	[thread overview]
Message-ID: <81b2fa44-feae-4ddd-80bf-fd6b0e5fe852@siemens.com> (raw)

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
-- 
Siemens AG, Technology


             reply	other threads:[~2024-04-05  8:39 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) [this message]
2024-04-05  9:09 ` Anton Mikanovich
2024-04-05  9:57   ` Uladzimir Bely
2024-04-05 10:03     ` Scheler, Fabian
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=81b2fa44-feae-4ddd-80bf-fd6b0e5fe852@siemens.com \
    --to=fabian.scheler@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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