From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] doc: Describe devshell_nodeps target
Date: Thu, 06 Feb 2025 10:41:31 +0300 [thread overview]
Message-ID: <2fd4508ebc724a46fffdcc2a002dfdf2e3c17416.camel@ilbers.de> (raw)
In-Reply-To: <e370bc21-0c49-4f98-8498-2351afd21729@siemens.com>
On Wed, 2025-01-22 at 07:08 +0100, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> This is a valuable tool to debug transitive build dependency issues.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> doc/user_manual.md | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index 62d16c8c..be71ef50 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -1151,6 +1151,10 @@ recipes. This target opens a terminal inside
> the schroot rootfs that runs the
> package build. To invoke it, just call
> `bitbake mc:${MACHINE}-${DISTRO}:<package_name> -c devshell`.
>
> +To debug build dependency issues, there is also the devshell_nodeps
> target. It
> +skips any failing dependency installation, allowing to run them
> manually in the
> +schroot.
> +
>
> ## Using ccache for custom packages
>
> --
> 2.43.0
>
Applied to next, thanks.
--
Best regards,
Uladzimir.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/2fd4508ebc724a46fffdcc2a002dfdf2e3c17416.camel%40ilbers.de.
prev parent reply other threads:[~2025-02-06 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 6:08 'Jan Kiszka' via isar-users
2025-02-06 7:41 ` Uladzimir Bely [this message]
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=2fd4508ebc724a46fffdcc2a002dfdf2e3c17416.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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